A customer has modified the C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\[login to view URL] file manually before we became involved.
He added the following string to it
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:[login to view URL]">
<dependentAssembly>
<assemblyIdentity name="[login to view URL]"
publicKeyToken="bdda2d694ae22a86"
culture="neutral" />
<bindingRedirect oldVersion="6.1.1.532"
newVersion="6.1.1.639"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
which causes the previous version of the software (superoffice , a german crm program) to work but which causes the next version of the software not to work anymore.
When we remove this string from the [login to view URL] file, the new version of the application works.
Is it safe to add the removal of this string to the installation package of the new software version.
We can always put a backup action of the original file to the script as well.
If not do, do you see any alternative to solve this issue ?