I have an assembly named AccountingLogic.dll which is referenced by over 15 different ASP.NET applications. On my production server that runs all the .NET apps, there are multiple versions of this assembly in the GAC, all with the same Public Key Token. My older sites are using older versions of the .dll, and my newer sites are using a newer version. The GAC on the production server looks somethinglike this...
Global Assembly Name Version Public Key Token
AccountingLogic.dll 1.1.0.0 b35F047de3de
AccountingLogic.dll 1.1.5.0 b35F047de3de
AccountingLogic.dll 1.2.0.0 b35F047de3de
The production server works fine, and is able to successfully hold multiple assembly versions in the GAC. However, my localhost cannot seem to do this. Whenever I have more than one version of the assembly in the GAC of my localhost, I encounter all kinds of weird problems when running apps locally. Essentially it seems like I can only have one version of AccountingLogic.dll in the GAC of my localhost, while the server can have an multiple versions. Why is this? Why can the server have different versions but my localhost cannot?
Thanks.
Global Assembly Name Version Public Key Token
AccountingLogic.dll 1.1.0.0 b35F047de3de
AccountingLogic.dll 1.1.5.0 b35F047de3de
AccountingLogic.dll 1.2.0.0 b35F047de3de
The production server works fine, and is able to successfully hold multiple assembly versions in the GAC. However, my localhost cannot seem to do this. Whenever I have more than one version of the assembly in the GAC of my localhost, I encounter all kinds of weird problems when running apps locally. Essentially it seems like I can only have one version of AccountingLogic.dll in the GAC of my localhost, while the server can have an multiple versions. Why is this? Why can the server have different versions but my localhost cannot?
Thanks.