Missing Assembly References in Visual Studio (Typically After Updating)
The problem typically occurs after updating the Test Studio Visual Studio plugin. In Visual Studio, your test projects will no longer build because of missing ArtOfTest Assemblies.
When you open the References folder in Solution Explorer, some of the referenced assemblies might have a yellow warning icon signifying they cannot be resolved:
When you add your first test to a new test project in Visual Studio, references to the required assemblies are automatically referenced. By default, Visual Studio references assemblies stored in the GAC (Global Assembly Cache) with their specific version number. When you update Test Studio, all of its assemblies are replaced. The replacements carry a newer version number even though they might not contain any differences.
Because of the difference in version number, the GAC sees these replacement files as different assemblies. It assumes the assemblies needed to build the project are now missing (cannot be resolved) and your project does not build.
Make the Reference version unspecific.
Open your test project in Visual Studio.
- Go to Solution Explorer.
- Expand the project and open the References folder.
- Select the references with a yellow warning icon. If none of them have yellow warning icons, then select them all.
- Right click on the selected assemblies and choose Properties from the context menu.
Check the Specific Version property. Change it to False. The yellow warning icons for the selected references should disappear.
You must select all the unresolved references at once or repeat these steps for every unresolved reference. Once you're done, there should be no warning icons and your project should build successfully.
Note: You may need need to manually remove ArtOfTest.Common if you upgrade from any 2010 build to a 2011 build. Test Studio attempts to remove it automatically but does not always succeed.
Also ensure you select either .NET Framework 3.5 or .NET Framework 4.0 as the target framework from the properties of the Test Project. We do not work with the Client Profile frameworks.