So far as I know, there's no way--documented or otherwise--to do this sort of redirection. If you think about it, if there was, it'd be a fairly serious security hole. "Hmm, let me redirect that request for mscorlib to EvilHackers.mscorlib-with-secrity-holes.dll...."
What you might look to do is instead recompile the application against your new version of the open-source DLL, since technically you're now forking the open-source component, making it into something different. About the best you could come up with is to re-compile the existing open-source component with your own pub/priv keypair, then sign the second version with the same pair. But, in general, the strong-name portion of the assembly is not considered to be part of the "evolvable" portions of the assembly name. Ted Neward Author, Presenter, Consultant Java, .NET, XML services http://blogs.tedneward.com > -----Original Message----- > From: Discussion of advanced .NET topics. [mailto:ADVANCED- > [EMAIL PROTECTED] On Behalf Of Bill Bassler > Sent: Wednesday, December 28, 2005 12:30 PM > To: [email protected] > Subject: Re: [ADVANCED-DOTNET] Is it possible to redirect binding to > another public key token? > > I don't have a copy of the key file/private key. This is actually the crux > of issue as whole. A related issue is if it's possible to redirect > existing > deployed assemblies that were compiled against the original assembly to > load the newly compiled assembly (that was built using another > public/private key pair that I don't have access to)without having to > recompiled them. I'm just trying to confirm if it is possible or not. > > Regards, Bill > > =================================== > This list is hosted by DevelopMentorR 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
