Rename DLL after it is compiled

[Jed]

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.

[Brock Allen]

You should read up on .NET assembly resolution semantics:

http://msdn.microsoft.com/library/de...asp?frame=true

-Brock
DevelopMentor
http://staff.develop.com/ballen

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.