We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy.
Unfortunately, activation email could not send to your email. Please try again.
Platform : Windows Forms
|
Category : Deployment

What are the common issues in redirecting assemblies using the publisher policy files?

1) Make sure to follow proper naming conventions for the policy dll. For example, if the original assembly name is TestAssembly.dll then the corresponding policy assembly should be called "policy.1.0.TestAssembly.dll" to make this redirection work for all "1.0.*" version bindings of the original assembly.

2) While specifying the name for the assembly in the policy file, do not include the ".dll" extension.

This is wrong: Instead use:

3) Make sure to sign the policy assembly with the same strong name as the original.

4) Make sure to distribute the policy file along with the policy assembly. Installing the policy assembly in the GAC alone will not suffice. Note that any change made to the policy file after creating the policy assembly will not take effect.

5) Always use /link (to the policy file) in the "al" command while creating the policy assembly. Do not use /embed. It doesn’t seem to be supported.

Some good links:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconcreatingpublisherpolicyfile.asp

http://www.newtelligence.com/downloads/downloads-basta2001.aspx

http://www.only4gurus.com/DotNet/studies/managevers.htm

You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.