It sounds like maybe Module2.dll is not getting deployed next to Program.exe.

Are these all 'project references' in visual studio, or 'assembly references'? Do you see the same behavior when you build the solution from the command-line using MSBuild?

By on 2/3/2009 1:33 PM ()

It sounds like maybe Module2.dll is not getting deployed next to Program.exe.

Are these all 'project references' in visual studio, or 'assembly references'?  Do you see the same behavior when you build the solution from the command-line using MSBuild?

Ah I found the problem. It looks like: A.dll -> B.dll -> C.dll. But, the AssemblyName of B.dll was C. So, the compiler was only deploying C.dll (even in bin/Debug for B.dll)

This was clear when examining the compiler output for B.dll (which I missed at first). It said: B -> C:\..[snip]..\bin\Debug\C.dll.

Is there a ``proper'' way to handle assemblies with the same name? (e.g. compiler error)

Thanks for your help.

By on 2/3/2009 2:29 PM ()

I found another post which might be related: [link:cs.hubfs.net]

By on 2/3/2009 12:12 PM ()
IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy
Built with WebSharper