471,306 Members | 867 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,306 software developers and data experts.

Policy file question

I have a dll, which is version, with the last part being the
auto numbered part. It has been installed in the GAC and there are a couple
of .net exe's using it. I now want to update the dll, to version
1.0.1.xxxxx, and update the component on the server where it is installed.
When I create the msi package, using VS .net 2003 installer, I can create an
msi that automatically updates the assembly and removes the previous
version. This is the desired result.
Now I do not want to update the applications that use the dll, but
instead create a policy file to deploy with the updated dll. I believe I
understand most of the policy file requirements and settings except for the
version number. The dll, and the setup msi version are manually updated, the
last part is auto generated, the .xxxxx. Can I leave off the last 5 digits
of the version number in the policy file? Since I do not know exactly what
the version number is going to be until I build the install?
For example, can I do the following:
<bindingRedirect oldVersion="1.0.0-1.0.1"

Instead of:
<bindingRedirect oldVersion=""

I would like to build and deploy the policy file with the new app
automatically. So my thought was when I build the installer project, which
builds the dll assembly first, I tack on post installation event to build
the policy file after the dll build.

Any problems or suggestions?

Jul 21 '05 #1
0 922

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Rob Barnes | last post: by
reply views Thread by andrew.noel | last post: by
1 post views Thread by cmrchs | last post: by
reply views Thread by Scanner2001 | last post: by
3 posts views Thread by =?Utf-8?B?SmFtZXMgV29uZw==?= | last post: by
1 post views Thread by =?Utf-8?B?U2NvdHQ=?= | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.