Home/ Questions/Q 7075063
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T06:07:57+00:00

My VS2010 solution has a test project in it. The unit tests themselves reference

  • 0

My VS2010 solution has a test project in it. The unit tests themselves reference the following namespace:

using Microsoft.VisualStudio.TestTools.UnitTesting;

which is accessed via the following assembly on my PC:

Assembly Microsoft.VisualStudio.QualityTools.UnitTestFramework
    C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\
    PublicAssemblies\Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll

When I build the solution on my PC I have no issues; the tests will build and run okay.

We have an intranet page which we can use to kick off builds on a build server. When I build via this page, the build fails with the following errors:

Generator.cs(3,17): error CS0234: The type or namespace name 'VisualStudio' 
does not exist in the namespace 'Microsoft' (are you missing an assembly
reference?)

The obvious problem would be that the Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll mentioned above is not present on the build server. I thought this was would be installed with VS2010, and since the projects in my solution build .NET 4.0 targets, I would expect this to be installed on the build server.

What is the easiest way to resolve this? The build server is out of my jurisdiction and I don’t particular want to log a job to get new libraries installed on to it.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The .UnitTestFramework.dll sits in C:\Program Files… folder and you have a reference to it.

    1. Create directory under your source control eg. Source/Binaries
    2. Copy the said dll into Source/Binaries
    3. Remove the reference to .UnitTestFramework.dll from your unit test assembly
    4. Add the reference to .UnitTestFramework.dll to your unit test assembly but this time select the dll that is now under Source/Binaries

    After that you can checkin your changes (make sure the Source/Binaries folder is checked in) and build the solution. When build server builds the solution it should get the dll from the source control.

    • 0