VS reports warning "WMC9999: Type universe cannot resolve assembly" from xaml compiler
See original GitHub issueVersion used: Visual Studio 16.7 Preview 6 WinUI 3 Preview 2 .NET 5 SDK Preview 7 (x64 only)
Reproduce:
It doesn’t reproduce for templated project, but reproduces for my simple scaffold project.
There’s warning WMC9999: Type universe cannot resolve assembly: WinRT.Runtime, Culture=neutral, PublicKeyToken=null.
for every xaml file shown in VS error list window, but not in VS build output.
It seems to be caused by setting <BaseIntermediateOutputPath>
in Directory.Build.props
, but I cannot eliminate the warning completely by commenting it out.
The attachment is reproduction project.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Type universe cannot resolve assembly: System. ...
I was able to resolve this by checking "Automatically check for missing packages during build in Visual Studio" (the "Allow NuGet to ...
Read more >XamlCompiler error WMC1006: Cannot resolve Assembly ...
On building UWP, am getting below message in VS studio XamlCompiler error WMC1006: Cannot resolve Assembly or Windows Metadata file 'System.Runtime.dll'
Read more >Type universe cannot resolve assembly
The using of DevExpress.UWP library requires installation of System.ComponentModel.TypeConverter, Version=4.2.1.0 library. Version 4.2.1.0. is ...
Read more >Cannot resolve Assembly or Windows Metadata file ...
Common.targets(264,5): Xaml Internal Error error WMC9999: Type universe cannot resolve assembly: Windows.Foundation.UniversalApiContract ...
Read more >Xamarin Challenge
After installing that I get an error saying it can't find the ... Error warning WMC9999: Type universe cannot resolve assembly: System.
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 FreeTop 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
Top GitHub Comments
Looks to be solved in preview 3.
I may as well add that I have been seeing this warning since preview version 1 as well as the other two in this screenshot. I hadn’t reported them yet because I have been using .Net 5.0 preview 7 with WinUI and as we know, that’s not the currently supported version. Since there doesn’t seem to be a way to have side-by-side installations of previews of .Net (that I am aware of) I didn’t take the time to uninstall, roll back and then revert the process when I was done. Thanks to @huoyaoyuan for reporting it. You can find a project that replicates the warnings at https://github.com/jtbrower/WinUI .