Why Publisher Policy file exists if same thing can be achieved using Machine.config file?
As far as I know, the machine.config file is the master configuration file on your system with a lot of default settings. Suppose we are having lot of applications using a particular assembly (1.0.0.0). Now, we need to make all the applications to use an
upgraded assembly (2.0.0.0). We can achieve this by including assembly binding information in machine's config file. These redirection settings in machine config file will override the application config and publisher policy settings.
But if we use publish policy file it will only work with one application..
Best Regards,
Brando
.NET forums are moving to a new home on Microsoft Q&A, we encourage you to go to Microsoft Q&A for .NET for posting new questions and get involved today.
Member
68 Points
240 Posts
Publisher Policy File
Jan 26, 2018 06:18 PM|vinodkpasi|LINK
Why Publisher Policy file exists if same thing can be achieved using Machine.config file?
Star
9831 Points
3120 Posts
Re: Publisher Policy File
Jan 29, 2018 07:44 AM|Brando ZWZ|LINK
Hi vinodkpasi,
As far as I know, the machine.config file is the master configuration file on your system with a lot of default settings. Suppose we are having lot of applications using a particular assembly (1.0.0.0). Now, we need to make all the applications to use an upgraded assembly (2.0.0.0). We can achieve this by including assembly binding information in machine's config file. These redirection settings in machine config file will override the application config and publisher policy settings.
But if we use publish policy file it will only work with one application..
Best Regards,
Brando