I have obtained next error message from Document! X 2010 when I tried to build XML documentation:
Could not load file or assembly 'DataDynamics.Analysis.Frontend, Version=1.0.912.0, Culture=neutral, PublicKeyToken=d557f2f30a260da2' or one of its dependencies. The system cannot find the file specified.Build process was Cancelled - 'An unexpected error was encountered'The main problem is: there is no Frontend assembly. Our product use {smartassemby} to merge this assembly to another one. You can download trial version of our product from site: http://www.datadynamics.com/Products/DDA/Releases.aspx{smarassembly} cannot merge XML documents, so we merged thier manually and they contains no references to Frontend assembly. Nor Reflector, nor IL DASM show any dependencies from Frontend assembly.I don't know, how Document! X 2010 process assembly, so can you suggest, where is the problem, and how it can be fixed.Thanks for any help.
Date
Votes
3 comments
-
Permanently deleted user This error is raised by .NET reflection and indicates a failure to resolve that type. It may be that SmartAssembly "hacks" the type resolution process at runtime to implement the embedding mechanism. That's one reason why it can be problematic trying to document obfuscated assemblies - they are often specifically designed to prevent analysis.
We would strongly recommend that you document from the un-obfuscated assembly.
If you send through a copy of the assembly to support@innovasys.com we can pinpoint the member that contains the missing type info. That won't resolve the issue, but it would allow you to see in reflector the problem member for your own information.
This forum is for peer to peer support and although we do monitor them it's not the best place to submit support requests. If you have any further support issues could you please send them through to support@innovasys.com so that they can be tracked (as you have done in the past). Thanks.
-
kimNathans I think, this error cannot be raisen by .NET reflection: this assembly is normal assembly without additional "hacks" and reflection works fine (we have NUnit tests). Can you provide correct code snippet, which you are using?
I cannot use un-obfuscated assemblies, because we use merging and public members can go from different initial assemblies.
Anyway: thanks for replay - I will send you additional information with affected assemblies.
-
Permanently deleted user The exception is definitely raised by .NET reflection. Please forward the assemblies and we can investigate further in the support channel.
Please sign in to leave a comment.