Can not find System.Windows Assembly

77,001

Solution 1

In my case there was no System.Windows reference available to pick up.
I had to include a reference to WindowsBase

Solution 2

Add the assembly reference as you'd add any other framework assembly reference:

  • Right-click on the project
  • Select "Add reference"
  • Select the .NET tab on the left, and find "System.Windows" in the list of assemblies
  • Double-click on "System.Windows" and the assembly reference will be added

Solution 3

Add System.Windows assembly reference:

  • Right-click on the project
  • Select "Add reference"
  • Select the .NET tab on the left, and find "System.Windows" in the list of assemblies
  • Double-click on "System.Windows" to add it

If this does not solve the issue try Adding PresentationFramework, PresentationCore and WindowsBase assemblies (.NET 3.5)

Solution 4

I had this occur on a machine with VS 2010 once before. For some reason, the System.Windows assembly was not found in the .NET tab of Add Reference window. Very strange.

In this case, you will just have to go to the Browse tab and navigate to:

C:\Windows\Microsoft.NET\assembly\GAC_MSIL\System.Windows\

Once there, select the proper version subfolder (should look something like... v4.0_4.0.0.0__b03f5f7f11d50a3a) and then choose the System.Windows.dll there.

Solution 5

I've found the needed WindowsBase.dll in

C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.0

Share:
77,001
Admin
Author by

Admin

Updated on February 15, 2020

Comments

  • Admin
    Admin over 4 years

    This is the error we get:

    Error 1 The type 'System.Windows.Point' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.Windows, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e'. C:\PacMan\PacMan\PacMan\PacManTests\UnitTest1.cs 65 13 PacManTests

    We get this error in our unit test project which cant find the System.Windows Assembly but our main project can find the assembly and run it fine.

    Does anyone have any input or advice on where or how we can reference System.Windows to fix this problem?