Is there any way to Assembly.Load() dynamically the DLLs of my project, with
their strong names, but without the need to specify a version? I just want
the public/private key to exist as a measure of safety for their
authenticity. I don't want to narrow down the valid DLLs to only those that
share the same version.
Because if later i decide to upgrade a DLL, I'll have to recompile and send
to the customer the WHOLE project, and not just the newer DLL, because its
version will differ from the others...
Thanks!
Bruce Johnson - 12 Dec 2004 05:19 GMT
You might want to take a look at the bindingRedirect tag in the
dependentAssembly section of app.config. It allows you to change the
version of a particular assembly that the CLR looks for when executing
an application. I suspect this is exactly what you're looking for.
Bruce Johnson [.NET MVP]
http://www.objectsharp.com/blogs/bruce
Dino Chiesa [Microsoft] - 13 Dec 2004 18:12 GMT
yep, your installer can copy the DLL in, and modify the settings in
app.config to specify the new version.
> You might want to take a look at the bindingRedirect tag in the
> dependentAssembly section of app.config. It allows you to change the
[quoted text clipped - 6 lines]
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!