Note: Upgrading large projects from 2.0.0 to 2.1.1

Brent posted on Wednesday, December 13, 2006

Just thought I would put this in the system so it is searchable by anyone running into any problems while moving to 2.1.1.

We have large projects with a lot of shared assemblies many of which reference Csla.  While attempting to test with 2.1.1 we ran into the issue of dependent assembly manifests not matching versions.  We were able to avoid this by adding the following to our project config files:

<?xml version="1.0" encoding="utf-8" ?>

<configuration>
      <runtime>
            <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
                  <dependentAssembly>
                        <assemblyIdentity name="Csla"
                                                  publicKeyToken="93be5fdc093e4c30"
                                                  culture="neutral" />
                        <bindingRedirect oldVersion="2.0.0.0"
                                                 newVersion="2.1.1.0"/>
                  </dependentAssembly>
            </assemblyBinding>
      </runtime>
</configuration>