Open sbanni opened 4 years ago
Hello sbanni, thank you for opening an issue with us!
I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌
@marb2000
@sbanni does this cause build errors or it's just a warning?
Same issue today trying to test https://docs.microsoft.com/en-us/windows/apps/desktop/modernize/host-custom-control-with-xaml-islands
Severity Code Description Project File Line Suppression State Warning The referenced component 'C:\Users\username.nuget\packages\microsoft.toolkit.win32.ui.xamlapplication\6.0.1\build..\lib\uap10.0\Microsoft.Toolkit.Win32.UI.XamlHost.winmd' could not be found. App1
It's a warning, but Publish I get "An error has occured".
10.05.2020 11:38:50 System.AggregateException: One or more errors occurred. ---> System.Exception: Publish has encountered an error. We were unable to determine the cause of the error. Check the output log for more details. --- End of inner exception stack trace --- ---> (Inner Exception #0) System.Exception: Publish has encountered an error. We were unable to determine the cause of the error. Check the output log for more details. <---
System.Exception: Publish has encountered an error. We were unable to determine the cause of the error. Check the output log for more details.
===================
I have the same issue.
I repro it today and there is still this warning in the 6.1.1 update:
Severity Code Description Project File Line Suppression State
Warning The referenced component 'C:\Users\xxx\.nuget\packages\microsoft.toolkit.win32.ui.xamlapplication\6.1.1\build\..\lib\uap10.0\Microsoft.Toolkit.Win32.UI.XamlHost.winmd' could not be found. UWPApplication
@ocalvo, can you take a look?
The same warning is still in Version 6.1.2, but I was able to publish with a self-signed cert, targeting x64, without errors.
When I remove this entry from the references list the warning goes away and the program compiles and runs without error. Unfortunately at every restart of visual studio the reference comes back. Is this perhaps a VS issue and not an issue with the toolkit at all?
Any word on this? I am getting sick of having to delete this reference multiple times a day and I don't like to just ignore warnings
@marb2000 @ocalvo any updates?
@marb2000 @ocalvo any updates, this is still a problem.
Same problem, 2023.
Create a C# WPF Core application and make sure package references are enabled.
Use the NuGet Package Manager window to install package "Microsoft.Toolkit.Wpf.UI.Controls", version is v6.0.0 or later.
Configure the target from "any cpu" to "x64".
Add a UWP project to the same solution, make sure the target version and minimum version are both set to "Win10 version 1903" or later.
Use the NuGet Package Manager window to install package "Microsoft.Toolkit.Win32.UI.XamlApplication", version is v6.0.0 or later.
Replace the content of app.xaml with the following code, make sure to replace MyUWPApp with your UWP project name.