0

Problems with Document!X for .NET 4.0 (Type load error)

brenneri

10 August 2010 06:32

None

Follow

I try to create a reference documentation for a .NET 4 class library  based on a Document!X (Net 4.0) project.  For one of the input assemblies (say A), the reference for a public class is is not generated - its signature being: public class SearchProperty : INotifyPropertyChanged {...}. To be more precise: the class is just not recognized. In the content editor for the assembly it does not appear (there is nothing special about it; it exposes one public property).

A second assembly (B) references the SearchProperty class, but I cannot add this second assembly to the Document! X project because it is not able to locate the class. There is an exception saying: "System.TypeLoadException. Could not load type ...SearchProperty from assembly A..."  (Document! X obviously knows where to look for the class).

When I build the Document! X project (leaving aside assembly B), I get a "FileNotFoundException: Could not load file or assembly B..." because some other assembly in the project refernces assembly B.

So, there is no chance to build my document. Do you have any idea what may go wrong (I tried a lot; I also think about older versions of the assemblies still available in the GAC - though the project explicitly uses assemblies from a local folder)?

Remark: Inspecting / editing the documentation for class SearchProperty within Visual Studio 2010 is no problem.

 

• Facebook
• Twitter
• LinkedIn

6 comments

• 0
  
  Richard Sloggett 10 August 2010 06:51

  It sounds very much like an older version of your assembly is being used. The most likely cause is a version in the GAC - .NET will use the GAC version in preference to an assembly in the same directory.

  If that isn't the problem, please drop us an email to support@innovasys.com so we can help further.

• 0
  
  brenneri 25 October 2010 08:06

  Meanwhile the problem vanished - just because I got a new computer with a new and clean environment. Basically, the problem still exists: what is required is a way to force Document! X to use exactly the assembly that is being referenced in  the project (I add a specific file to the project, and I surely want the help document be generated from this file, and not from "some" version of the file which is may also be around).

  Best regards

   

• 0
  
  Richard Sloggett 25 October 2010 08:26

  .NET will always use a GAC version of an assembly in preference to a local file, and this isn't something that is overridable I'm afraid. The best approach is to ensure that your assemblies are not in the GAC on the machine on which you are documenting them.

• 0
  
  brenneri 26 October 2010 10:17

  Document!X knows the absolute path of the assembly - it should not be too difficult to explicitly load the assembly from this path instead of letting .NET make a guess. When  I add a assembly to the dxp project I want this one to be analyzed - not an arbitrary one. At least I should have a choice.

• 0
  
  Richard Sloggett 27 October 2010 05:24

  If you have a strong named assembly present in the GAC, then .NET will always use that version in preference to a local one. The solution to this is to remove the copy from the GAC if you want to document a different version.

• 0
  
  Etienne Martin 12 December 2010 08:17

  Hello,

  I am having a similar problem when wanting to document a Silverlight 4.0 assembly by adding it to my project. I get getting multiple typeload errors, usually file not found, but also, parent not found exceptions when adding the reference.  I have the December 1, 2010 release of DocumentX and Visual Studio 2010 with the most recent Silverlight updates.  I have no errors when loading a regular framework 4.0 dll, such as the web services or my WPF client

  As suggested above, I've checked my project file's references and the Silverlight dependencies are all referenced properly in the project  by full path, in my case:

  C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\Silverlight\v4.0

  I have attempted to set the flag on the referenced libraries to copy local, with no success (same load errors).  I have verified the libraries in question are not in the GAC.

  I can easily duplicate the error by loading the assembly System.Windows.dll from the above path.

  This only happens when I try to add any Silverlight 4.0 assembly to my DocumentX project - either delivered or ones I've created.

  Any help would be appreciated as I really need to be able to document Silverlight projects as simply as I can the others.  

   

  Regards,

   

  Etienne