J
Joe HM
Hello -
I have the following problem. An executable uses a strong-named DLL
that is in the GAC. So every time I update the DLL, I have to rebuild
the *.exe. This is something I would really like to avoid since I have
to re-distribute the *.exe every time.
I tried to create a XXX.exe.config file that looks as follows ...
<configuration>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="DUMMY" publicKeyToken="SOMETHING"
culture="neutral" />
<bindingRedirect oldVersion="1.0.0.0" newVersion="1.0.0.1"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>
The oldVersion is the DLL version with which I built the *.exe and the
newVersion is the version of the new DLL.
This works fine but now I have to distribute the XXX.exe.config file
every time I update the DLL.
Is there a way to use a wildcard for the newVersion to use something
like newVersion="1.0.0.*" so that it works with every *.dll version
1.0.0.*?
Thanks!
Joe
I have the following problem. An executable uses a strong-named DLL
that is in the GAC. So every time I update the DLL, I have to rebuild
the *.exe. This is something I would really like to avoid since I have
to re-distribute the *.exe every time.
I tried to create a XXX.exe.config file that looks as follows ...
<configuration>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="DUMMY" publicKeyToken="SOMETHING"
culture="neutral" />
<bindingRedirect oldVersion="1.0.0.0" newVersion="1.0.0.1"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>
The oldVersion is the DLL version with which I built the *.exe and the
newVersion is the version of the new DLL.
This works fine but now I have to distribute the XXX.exe.config file
every time I update the DLL.
Is there a way to use a wildcard for the newVersion to use something
like newVersion="1.0.0.*" so that it works with every *.dll version
1.0.0.*?
Thanks!
Joe