Error "no reference set to an instance of an object..."

This forum is for all Flare issues related to the Microsoft HTML Help target.
This target produces "CHM" files in the output.
Post Reply
Brit
Propeller Head
Posts: 12
Joined: Thu Sep 20, 2007 7:00 am

Error "no reference set to an instance of an object..."

Post by Brit »

I am using Flare 2.5 to compile HTML help. In my English project I've made some changes, added snippets to use in several files. Now when I want to compile, during the "Resolving links in output files..." process the compiling is aborted. I tried everything: created a test project, deleted files and folders... The message is because of one of the folders I worked in before. If I delete the folder completely, the message disappears. But I cannot detect which of the sub folders or subtopics is the reason for the error. The message disappears when I delete all sub folders in that folder except of one - it does not matter which one.
It seems to me that either the folder size is too big or is it a basic problem which cannot solved easily but creating the folder and file structure again? Is there any restriction to the size or complexity of folder structures in Flare? Does anyone know about this?
Brit
Propeller Head
Posts: 12
Joined: Thu Sep 20, 2007 7:00 am

Re: Error "no reference set to an instance of an object..."

Post by Brit »

I found the solution by myself. The problem was an unlinked reference in a snippet. During compilation the process aborted suddenly when resolving links it said. Unresolved links in usual topics are displayed but not that kind of links in snippets. This is quite difficult to find, I think. Wouldn't it be much easier to know where the problem is by showing it in the messages/errors report clearly?
RamonS
Senior Propellus Maximus
Posts: 4293
Joined: Thu Feb 02, 2006 9:29 am
Location: The Electric City

Re: Error "no reference set to an instance of an object..."

Post by RamonS »

That is one of my pet peeves for a long time, not only with MadCap's software. Proper error reporting is a lot of tedious work that does not add any functional value, which is why most developers just don't care. After all, when an error comes up it is the support team who has to deal with the mess. I coined a term for this: developer arrogance.
Post Reply