How to automatically generate many publisher policies ?

[Seb LM]

Hello,

I'd like to define a publisher policy which covers many versions of
assembly from which the "major.minor version" are different but it's not
possible to make a such publisher policy.
So it's necessary to create a publisher policy for each new "major.minor
version", which can take a long time to make manually.
Do there exist tools to generate publisher policy for many "major.minor
versions" from a simple and compact configuration file ?

Thank you for your assistance,

-- Seb LM

[David Levine]

For an application configuration file you should be able to specify a range
of versions all redirected to the same assembly. An xml snippet...

<bindingRedirect oldVersion="0.0.0.0-1.2.3.4" newVersion="1.2.3.4"/>

will redirect all binds up through version 1.2.3.4 to the same assembly
version 1.2.3.4

I believe a publisher policy file allows the same syntax.
"Seb LM" <sl**********************@antispam.antispam> wrote in message
news:OV**************@TK2MSFTNGP11.phx.gbl...

Hello,

I'd like to define a publisher policy which covers many versions of
assembly from which the "major.minor version" are different but it's not
possible to make a such publisher policy.
So it's necessary to create a publisher policy for each new "major.minor
version", which can take a long time to make manually.
Do there exist tools to generate publisher policy for many "major.minor
versions" from a simple and compact configuration file ?

Thank you for your assistance,

-- Seb LM