ansaurus

Question

"Could not load file or assembly"/ "or one of its dependencies. The module was expected to contain an assembly manifest."

Answer 1

A:

I'm not sure if this will help you or not, but I have stumbled on this thread:

http://social.msdn.microsoft.com/Forums/en/vsdebug/thread/9ad17869-63cc-4529-bfaf-9099db500e0d

It appears that a few people have seen this error when building / running assemblies with the same name, so for example:

SomeAssembly.exe
SomeAssembly.dll

Could this be applicable in your case?

Kragen 2010-01-05 11:02:53

No, this is not applicable.

Susanta Samanta 2010-01-05 11:39:46

Answer 2

+1 A:

The SharpSvn-DB44-20-Win32.dll is an optional helper dll for SharpSvn.dll. It contains only unmanaged code.

It contains support for directly accessing BDB repositories on the filesystem. You don't need this DLL if you only use fsfs (file://) and/or remote repositories.

The SASL dll is also optional, but you need that when you want to use svn:// repositories.

Bert Huijben 2010-01-05 12:06:06

If I only use sharpsvn dll or nServicebus dll in my project then no problem occurs, but when I use both SharpSvn and Nservicebus then(only executing time, not compile time) the above error throws.Kindly give a solution.

Susanta Samanta 2010-01-05 12:54:13

Answer 3

+2 A:

Exclude the sharpsvn dlls from the NServiceBus assemblyscanning by configuring NSB with a explicit list of assemblies toi scan:

Configure.With("List of your assemblies that contain messagehandlers")...

Make sure to include NServiceBus.core.dll in the list if you're using the Saga feature.

Hope this helps!

Andreas 2010-01-05 13:33:45

I have configure three dll(NServiceBus.dll,NServiceBus.core.dll,NServiceBus.ObjectBuilder.CastleWindsor.dll) ,then this error is commingType NServiceBus.Unicast.Transport.CompletionMessage was not registered in the serializer. Check that it appears in the list of configured assemblies/types to scan.Please tell me why this error is coming?

Susanta Samanta 2010-01-06 07:56:17

The completion message lives in the core dll so you should be fine with the dll:s you mention. Try specifying the core assembly using: typeof(CompletionMessage).Assembly and see if that helps?

Andreas 2010-01-06 20:03:15

Can you please specify in details?

Susanta Samanta 2010-01-07 07:13:02

Can you post your initialization code here? (the Configure.With(...) stuff)

Andreas 2010-01-07 08:29:54

My code is bellow:myDllAssembly.SetValue(Assembly.LoadFile(@"..NServiceBus.dll"), 0); myDllAssembly.SetValue(Assembly.LoadFile(@"..NServiceBus.Core.dll"),1); myDllAssembly.SetValue(Assembly.LoadFile(@"..NServiceBus.ObjectBuilder.CastleWindsor.dll"), 2);Bus = NServiceBus.Configure.With(myDllAssembly).SpringBuilder().MsmqSubscriptionStorage() .XmlSerializer().MsmqTransport().IsTransactional(true).PurgeOnStartup(false) .UnicastBus().ImpersonateSender(false).CreateBus().Start();

Susanta Samanta 2010-01-07 08:45:43

try this instead:Configure.With(typeof(CompletionMessage).Assembly,typeof(OneOfYourOwnMessageTypes).Assembly,typeof(OneOfYourOwnMessageHandlers).Assembly)...NServiceBus scan the assemblies for messages and messagehandlers so there is no need to include the ObjectBuilder (NServiceBus.ObjectBuilder.CastleWindsor.dll)Let me know if that works!

Andreas 2010-01-08 12:58:09

Answer 4

+1 A:

Hi The problem get resolved by using the following bus configuration.

Bus = NServiceBus.Configure.With(typeof(IMessage).Assembly, typeof(CompletionMessage).Assembly) .SpringBuilder().MsmqSubscriptionStorage().XmlSerializer().MsmqTransport() .IsTransactional(true).PurgeOnStartup(false).UnicastBus().ImpersonateSender(false) .LoadMessageHandlers().CreateBus().Start();

Thanks to Andreas

Susanta Samanta 2010-01-12 09:29:29

Answer 5

+1 A:

Susanta,

We recently committed an additional API which can be things easier for you by allowing you to specify which assemblies not to load as follows:

Configure.With(AllAssemblies.Except("SharpSvn-DB44-20-Win32.dll"))... // rest of your config

Udi Dahan 2010-01-26 13:15:41

ansaurus

tags:

views:

answers:

"Could not load file or assembly"/ "or one of its dependencies. The module was expected to contain an assembly manifest."

related questions