dll version
-
My client exe refering a assembly dll version 1.o which is in GAC. As i found some bug in dll version 1.0, i corrected it and make it version 2.0.Now i want my client exe to refer 2.0 without compiling the client exe again.How to do this.
If you want to redirect all applications on a machine which use this assembly, you can use Publisher Policy[^] to redirect all uses of this assembly to the new version. Things to be aware of: The framework looks for a publisher policy file with the major and minor version of the assembly reference. If you patch this assembly again, calling it v3.0, and you want clients which need v1.0 and v2.0 to use v3.0, you'll need to ship policy.1.0.assemblyname.dll and policy.2.0.assemblyname.dll. I'd recommend keeping the same major and minor version numbers for patches, incrementing only the last two parts of the version number (build and revision). Only change the major and minor version number for breaking changes in the interface. You must use the same strong-name key to sign policy assemblies as the original assembly. You must set the version number on the policy assemblies. The GAC install process will silently fail to overwrite a policy assembly with the same or lower version number. It isn't fully clear in Microsoft's documentation - you CANNOT embed the policy XML file in the assembly DLL file. The assembly must link to the policy file. The publisher policy system is most useful for security patches. If you want to redirect a single application, you can use bindingRedirect[^] elements in the application's configuration file. You should generally default to not putting your own assemblies in the GAC. See this blog post[^] for reasons. Stability. What an interesting concept. -- Chris Maunder