Hello Fredrik,

Did u provide the publisher policy with your new assemblies? http://msdn2.microsoft.com/en-us/library/7wd6ex19%28vs.71%29.aspx

---
WBR,
Michael  Nemtsev [.NET/C# MVP] :: blog: http://spaces.live.com/laflour 

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

FP> Hi all
FP>
FP> I'm building an application that contains a dll that will be used by
FP> several
FP> other applications.
FP> The dll is installed in the GAC, to make it easy for everyone to
FP> find it.
FP> When my application is upgraded, I'm also installing a policy in the
FP> GAC so
FP> any call to the old dll is redirected to the new one.
FP> My problem is the following scenario;
FP>
FP> 1) My.dll 1.0.0.0 is installed in the GAC
FP>
FP> 2) My.dll is upgraded to 1.1.0.0 (replaces the previous version in
FP> the GAC)
FP> policy.1.0.My.dll is installed in the GAC, redirecting 1.0.0.0 to
FP> 1.1.0.0
FP> 3) My.dll is upgraded to 1.2.0.0 (replaces the previous version in
FP> the GAC)
FP> policy.1.1.My.dll is installed in the GAC, redirecting 1.1.0.0 to
FP> 1.2.0.0
FP> After step 3, when an application is trying to use My.dll version
FP> 1.0.0.0, it only gets redirected to My.dll version 1.1.0.0 and not
FP> to 1.2.0.0 which I wanted.
FP>
FP> Isn't it possible to use version redirection multiple steps?
FP> Do I need to add a new policy AND update my old policys everytime I
FP> upgrade
FP> the dll?
FP> Thanks!
FP> /Fredri