Hi,
I have an application that consists of multiple strong-named assemblies
like:
App.exe references Utils.dll (for simplicities sake)
All assemblies are strong-named, but not GAC'd (private assemblies).
My goal is that once I have deployed App.exe, I want to deploy a bugfix
in Utils.dll and redeploy this dependent assembly _without_ redeploying
App.exe.
Let's assume the interface of the types in Utils.dll have not changed.
I thought that I could redeploy my new strong-named Utils.dll along
with an codebase directive in App.exe.config redirecting to the new
assembly to use (and ignore the old one). E.g:
<configuration>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="Utils"
publicKeyToken="f6a8ba1bc21a01be"/>
<codeBase version="1.0.2081.19103" href="file://c:/program
files/myapp/hotfix/20050909/Utils.dll"/.
</dependentAssembly>
</assemblyBinding>
</runtime>
<configuration>
I don't get this to work. The error message I get is:
"The located assembly's manifest definition with name 'Utils' does not
match the assembly reference."
Quite frankly I'm not sure if redirecting assembly bindings work at all
for strong-named assemblies or only work for weakly-named assemblies.
Can anyone help me out here?
Thanks
-Stefan