Invalid nuget package dependency on MaterialDesignColors >= 1.1.0
See original GitHub issueEnvironment: Visual Studio Community 2017 Version 15.8.9
I am creating a simple WPF app following Getting Starting guide. I reference the MaterialDesignThemes nuget package which is 2.5.0.1205 It has a dependency MaterialDesignColors (>= 1.1.0)
So Visual Studio pulls MaterialDesignColors automatticaly and it is 1.1.0 which has no resources mentioned in the Getting Starting guide. There are no Themes/Recommended/Primary/...
or Themes/Recommended/Accent/...
resources.
Referencing manually MaterialDesignColors 1.1.3 solves the problem.
Issue Analytics
- State:
- Created 5 years ago
- Comments:14 (9 by maintainers)
Top Results From Across the Web
Unable to resolve dependencies of NuGet packages
When you upgrade the site by installing Telerik.Sitefinity.All NuGet package, Visual Studio throws the following error: Unable to resolve dependencies.
Read more >C# Nuget package wrong dependency
Actually, when you reference Newtonsoft.Json v12.0.3 , the right version of the dll is 12.0.0.0 . enter image description here.
Read more >Troubleshooting NuGet Package Restore in Visual Studio
csproj) or your packages.config file. (In Visual Studio, the references appear in Solution Explorer under the Dependencies \ NuGet or the ...
Read more >NuGet Package Dependency Resolution
Details on the process through which a NuGet package's dependencies are resolved and installed in both NuGet 2.x and NuGet 3.x+.
Read more >Visual Studio deploys wrong NuGet package : r/dotnet
Sometimes nuget packages will have a strict dependency on a dll. This means that they will always pull in where version == x...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I can not reproduce this at my work station with VS 2017 Profesional Version 15.8.5 I will need some time to reproduce at home with Community Edition. I consider it is a VS issue. Will be back with details.
The issue is simple, it’s just a nuspec problem. MaterialDesignThemes 2.5.x depends on version 1.1.0 of MaterialDesignColors but the previous version 2.4.x on version 1.1.2. And theses files are missing in the 1.1.0 version. So if you use the new csproj you only reference MaterialDesignThemes and the system automaticaly reference the version 1.1.0 of MaterialDesignColors that is too old. As library consummer you can fix the problem in installing directly the last version of MaterialDesignColors package. As library developper you can fix it directly in the nuspec.
Before : Dependency 1.1.2 https://github.com/MaterialDesignInXAML/MaterialDesignInXamlToolkit/blob/e9200ba3d6cb1f24a679d7f0429b925caaf93eac/MaterialDesignThemes.nuspec
After : Dependency 1.1.* so 1.1.0 by default for nuget https://github.com/MaterialDesignInXAML/MaterialDesignInXamlToolkit/blob/9fa6c45bf4a63631a8acd0a61d70b04fe446f08b/MaterialDesignThemes.nuspec