I have a dll, which is version 1.0.0.23456, 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"
newVersion="1.0.2"/>
Instead of:
<bindingRedirect oldVersion="1.0.0.0-1.0.1.99999"
newVersion="1.0.2.24785"/>
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?
J
