Unknown build error Cannot resolve dependency to System.Windows

Question

I just downloaded PoshConsole\'s source code and was trying to build the solution. I initially had two problem -

1. the System.Interactivity.dll could not be

Answer 1

I have received this error message for another (non-GAC, custom) assembly.

In my case, the situation was as follows:

• assembly X contains class A
• assembly Y contains class B, which inherits from A
• assembly Z contains a data template for class B

Y referenced X, Z referenced Y.

The error message was pointing to the line in the data template in Z where B was referenced, and pointed out that X could not be loaded.

The solution was to have Z also reference X. Apparently, the compiler cannot resolve that transitive reference for loading the required assemblies on its own.

Answer 2

In your [projectName].csproj file, you can identify the non-resolvable dependency and remove it before add it again latter.

• This was my error: v4.0.30319\Microsoft.WinFx.targets(268,9): error MC1000: Unknown build error, 'Cannot resolve dependency to assembly 'Microsoft.Data.Schema',...
• in my .csproj file i identified the reference line with the key word 'Microsoft.Data.Schema'
• i deleted the line and my project was able to be build again.

Hope it will help others

Answer 3

I would like to add some information in addition to O. R. Mapper's answer that suggests adding a reference to the assembly that is indicated by the compiler error.

I experienced the same problem while working on a WPF project. Considering the X,Y,Z relation presented in his answer, the problem happens when binding properties with types from X to a DataTemplate with DataType from Y. So, this doesn't happen for all assemblies that are referenced by Z, but rather those that only expose their specific types within Views. In my case, I was binding SelectedItem of a ComboBox to an enum property declared in X.

You can refactor these types to object and the problem goes away if you really want to preserve references as they should, especially if you use MVVM. Furthermore, the problem goes away by itself when you properly wrap Model types into ViewModel ones, because that generates explicit code that helps Visual Studio figure out required assemblies.

Hope this helps.

Answer 4

I'm going to toss in and answer on this old question, in-case someone runs into the same issue.

I was recently working on a legacy program and had this error. The solution was not readily apparent.

Issue

One of the NuGet packages referenced was created for a bunch of internal libraries and stored on the internal NuGet repository.

The applications compiled fine on VS2013, due to all the NuGet references having in the Project files, directly to the libraries.

When these references were changed to (Does not support HintPath), many of these NuGet packages were not created according to nuspec. There was no lib folder.

The packages were remade to follow the spec, however several of the packages had old Silverlight libraries included in them. These libraries were causing the error.

Solution

Following nuspec, the lib folder had sub-folders created: net45 and sl4. .NET4.5 and Silverlight4.0 respectively.

When the packages were replaced with the new ones, the builds worked fine. Regardless of Project file version.

TL;DR

Old nupkg structure:

Package.1.0.0.nupkg
   - Library.Net40.dll
   - Library.Sl4.dll

New nupkg structure:

Package.1.0.1.nupkg
    - lib
        - net45
            - Library.dll
        - sl4.0
            - Library.dll

Answer 5

That error generally means that you've added a reference to a Silverlight assembly within a WPF project - the two can't coexist.

See: Errors when referencing Silverlight class library from WPF application