Rename DLL after it is compiled

G

Guest

I have a DLL that I compiled to CodeAsset.dll.

The version is 1.1.0.0.

If I rename the file from CodeAsset.dll to CodeAsset.1.1.dll, reference it
in a web project, recompile the web project, and the newly named file is in
the bin directory, shouldn't the web project run fine?

I did this and instead I get the following error:
The located assembly's manifest definition with name 'CodeAsset.1.1' does
not match the assembly reference.

Why am I getting this error? I have tried various methods of adding the
file to the web.config compiler section, but they have not worked.

If I create a new release version (1.2.0.0) of my DLL and I want the two to
run side-by-side, I would have to rename the newly compiled version of the
dll file so CodeAsset.1.1 and CodeAsset.1.2 could run side-by-side? Unlikely
or rare I know, but possible if two different web projects are in the same
root and were compiled against different versions of the "same" dll.

I have searched all over and can't figure this out.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

How to write metainformation in asp.net dll 4
After project compiled what to do 1
Memory Leak only when compiled in Release mode. 1
Getting debugger line numbers from external assembly from ASP.Net 1
DLL & Bin folder hell. 1
Creating a User Control Library 3
XML comments in the DLL not showing 3
Assembly's manifest definition does not match the assembly reference 2

Top