Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>according to the <a href="http://support.microsoft.com/kb/917407" rel="noreferrer">microsoft support</a> you can use it by trick.</p> <p>Notes</p> <ul> <li>These steps upgrade or downgrade assembly A in the scenario that was described in the "How to upgrade or downgrade an assembly" section.</li> <li>This example assumes that the versions of the two assemblies are both 1.0.0.0 and the assemblies are both written in C#. When you follow these steps, you try to upgrade assembly A and assembly B to version 2.0.0.0.</li> </ul> <p>To upgrade or downgrade assembly A, follow these steps.</p> <ol> <li>Back up version 1.0.0.0 of assembly B to a folder.</li> <li>Modify and then recompile assembly B to version 2.0.0.0.</li> <li>Use the ALTER ASSEMBLY statement to upgrade assembly B in SQL Server 2005.</li> <li>Modify and then recompile assembly A to version 2.0.0.0. When you do this, reference version 1.0.0.0 of assembly B from the backup that you made in step 1. To do this, use the Csc.exe compiler tool together with the /reference switch. For example, use the following command: csc /target:library /out:AssemblyA.dll AssemblyA.cs AssemblyInfo.cs /reference:"BackupFolder\AssemblyB.dll" Note To verify the version of assembly B in the metadata of assembly A, open assembly A by using the Ildasm.exe utility. Then, verify the metadata information for the referenced assembly under the MANIFEST section.</li> <li>Use the ALTER ASSEMBLY statement to upgrade assembly A in SQL Server 2005.</li> </ol>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload