How do I tell the client applications that are already installed to start using this new MyApp.dll?
How do I tell the client applications that are already installed to start using this new MyApp.dll?
✍: Guest
So let’s say I have an application that uses MyApp.dll assembly, version 1.0.0.0. There is a security bug in that assembly, and I publish the patch, issuing it under name MyApp.dll 1.1.0.0. How do I tell the client applications that are already installed to start using this new MyApp.dll?
Use publisher policy. To configure a publisher policy, use the publisher policy configuration file, which uses a format similar app .config file. But unlike the app .config file, a publisher policy file needs to be compiled into an assembly and placed in the GAC.
2014-12-29, 1888👍, 0💬
Related Topics:
How can you debug failed assembly binds?
How can you debug failed assembly binds? Use the Assembly Binding Log Viewer (fuslogvw.exe) to find out the paths searched. 2014-12-19, 2125👍, 0💬
Where are shared assemblies stored?
Where are shared assemblies stored? Global assembly cache. 2014-12-19, 1981👍, 0💬
How can you create a strong name for a .NET assembly?
How can you create a strong name for a .NET assembly? With the help of Strong Name tool (sn.exe). 2014-12-22, 1910👍, 0💬
