The module was expected to contain an assembly manifest.

The module was expected to contain an assembly manifest.

SRSDS
Advisor Advisor
22,597 Views
1 Reply
Message 1 of 2

The module was expected to contain an assembly manifest.

SRSDS
Advisor
Advisor

Hi,

Can anyone explain this error when trying to NETLOAD a compiled dll. It's on a Windows 7 machine running 2009.

 

 

Cannot load assembly. Error details: System.BadImageFormatException: Could not

load file or assembly 'file:///C:\Program Files\Profile\Profile .NET3.0.dll' or

one of its dependencies. The module was expected to contain an assembly

manifest.

File name: 'file:///C:\Program Files\Profile\Profile .NET3.0.dll'

  at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase,

Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark,

Boolean throwOnFileNotFound, Boolean forIntrospection)

   at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef,

Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)

   at System.Reflection.Assembly.LoadFrom(String assemblyFile)

   at Autodesk.AutoCAD.Runtime.ExtensionLoader.Load(String fileName)

   at loadmgd()

WRN: Assembly binding logging is turned OFF.

To enable assembly bind failure logging, set the registry value

[HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

Note: There is some performance penalty associated with assembly bind failure

logging.

To turn this feature off, remove the registry value

[HKLM\Software\Microsoft\Fusion!EnableLog].

0 Likes
Accepted solutions (1)
22,598 Views
1 Reply
Reply (1)
Message 2 of 2

SRSDS
Advisor
Advisor
Accepted solution

I'm not sure which of these fixed this but..

 

There were a few reference dll files that I failed to bundle in with the project. Most likely the problem.

 

I also cleaned the project which was one suggestion I found. Build>Clean

 

0 Likes