Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 958925 - Last Review: October 17, 2008 - Revision: 1.0
Versioning the publisher policy file for your assemblies
Source: Microsoft Support
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.
Create and install an assembly A with a Version number (e.g. 1.0.0.0) in the GAC. Now you wish to install an updated version of A in the GAC, but this time with the same major/minor number in the assembly version (e.g. 1.0.0.1). Now also suppose you are providing the publisher policy file with all versions of assembly A to redirect the applications to the highest version of assembly A present in the GAC.
Â
See How to: Create a Publisher Policy: Â
http://msdn.microsoft.com/en-us/library/dz32563a.aspx
(http://msdn.microsoft.com/en-us/library/dz32563a.aspx)
 When you install the policy file for assembly version 1.0.1.0 in the GAC, this will overwrite the policy file you installed for assembly version 1.0.0.0 because both the policy files have the same name: “policy.1.0.mainAssemblyName.dllâ€
Note that policy files are named in the following format Â
policy.majorNumber.minorNumber.mainAssemblyName.dllResolve this problem by versioning the policy file the same as the assembly version, using the following command.Â
cmd> al /link:MyDll.dll.config  /v:1.0.1.0  /out:policy.1.0.MyDll.dll /keyfile:mykey.key
This will result in a policy file named “policy1.0.myDll.dll,†and when you install this in the GAC, use cmd> gacutil /i policy1.0.myDll.dll.
You see this version 1.0.1.0 with the policy file in the GAC.
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALSâ€) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
APPLIES TO
- Microsoft .NET Framework 2.0
- Microsoft .NET Framework 3.0
| kbnomt kbrapidpub kbhowto KB958925 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please