dll - Add CUI references bug -

i have big problem. need develop cui tests vs 2012. need use "old" (version 10.0.0.0) cui-dll's "microsoft.visual studio.testtool.uitesting". problem is, vs always references 11.0.0.0 versions. .csprj files have right entries like:

<when condition="'$(visualstudioversion)' == '10.0' , '$(iscodeduitest)' == 'true'">   <itemgroup>     <reference include="microsoft.visualstudio.qualitytools.codeduitestframework, version=10.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil">       <private>false</private>     </reference>     <reference include="microsoft.visualstudio.testtools.uitest.common, version=10.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil">       <private>false</private>     </reference>     <reference include="microsoft.visualstudio.testtools.uitest.extension, version=10.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil">       <private>false</private>     </reference>     <reference include="microsoft.visualstudio.testtools.uitesting, version=10.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil">       <private>false</private>     </reference>   </itemgroup> </when> 

deleting 11.0.0.0, cleaning solution , adding 10.0.0.0 version not help.. vs studio add 11.0.0.0 version...

hope can :)

to start with, conditional statement in .csprj file going use version 10.0.0.0 references if visual studio version 10.0.

you can delete section entirely , force references 10.0. may or may not work (vs 2012 tries "smart" references , use latest version available).

you can change .csproj <when> condition , remove reference visualstudioversion. again, may or may not work.

finally, in app.config can force version override:

  <runtime>     <assemblybinding xmlns="urn:schemas-microsoft-com:asm.v1">       <dependentassembly>         <assemblyidentity name="system.web.helpers" publickeytoken="31bf3856ad364e35" />         <bindingredirect oldversion="1.0.0.0-2.0.0.0" newversion="2.0.0.0" />       </dependentassembly>     </assemblybinding>   </runtime> 

this method can fail when you're trying force older reference.

regardless of method try, you'll want make sure existing files can restore them if accidentally mangle project.

what reason need use older versions? there may better options moving newer versions of dlls.