In a nutshell, You are trying the wrong approach to do the right thing. You have created a new version of an assembly and signed it with your strong name Key pair. I would follow the rules and information on versioning of .Net assemblies. That should give you the result you need without signing your assembly with someone else's "sn" key pair.
________________________________ From: Discussion of advanced .NET topics. on behalf of Bill Bassler Sent: Tue 12/27/2005 8:46 AM To: [email protected] Subject: [ADVANCED-DOTNET] Is it possible to redirect binding to another public key token? Is it possible ... Much in the same way that you can specify a binding redirect based on old and new assembly versions ... (within the same major and minor versions as a constraint per policy assembly) Can you also specify a binding redirect based on a different publickeytoken too? Or is this too against the notion of signing the assembly based on a private key? This doesn't appear possible based on the documented attributes for assembly binding redirects. I'm trying to redirect from an old open source signed assembly to a new version I've compiled using that open source with my private key. By way of example, something like the following. <?xml version="1.0"?> <configuration> <runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="MyCalledAssembly" oldpublicKeyToken="0556152c9715d60f" publicKeyToken="05SomeNewPublicKeyToken"/> <bindingRedirect oldVersion="1.0.0.0" newVersion="1.0.0.2" /> </dependentAssembly> </assemblyBinding> </runtime> </configuration> =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
