Open Vespion opened 8 months ago
@Vespion thanks for the report. We fixed this in later versions of Uno. Can you upgrade to the latest version and let us know?
I've updated all the packages, now I'm seeing an error during build
CONSOLE: Use build tool: C:\Program Files\dotnet\sdk\8.0.201\MSBuild.dll 18:10:35 Building I:\Programming\WinTest\WinTest.Windows\WinTest.Windows.csproj 18:10:35 Building I:\Programming\WinTest\WinTest\WinTest.csproj
...
Applying NuGet packaging workaround for dependent PRI files exclusion 0>MrtCore.PriGen.targets(913,5): Error MSB4062 : The "Microsoft.Build.Packaging.Pri.Tasks.ExpandPriContent" task could not be loaded from the assembly C:\Program Files\dotnet\sdk\8.0.201\Microsoft\VisualStudio\v17.0\AppxPackage\\Microsoft.Build.Packaging.Pri.Tasks.dll. Could not load file or assembly 'C:\Program Files\dotnet\sdk\8.0.201\Microsoft\VisualStudio\v17.0\AppxPackage\Microsoft.Build.Packaging.Pri.Tasks.dll'. The system cannot find the path specified. Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.
I think this might be similar #12013? However, I'm not sure how you're supposed to run the project through the IDE in that case.
Thanks for the update. This is indeed the same error, but this should not be a problem using Visual Studio. How do you get to this ? Do you use F5 to get this error?
No, I've been using the Unpackaged Application run configuration in Rider.
VS does work when using F5. I assumed this might be because VS calls MSBuild, not the dotnet CLI, but after checking, I noticed that Rider calls MSBuild directly, too.
No, I've been using the Unpackaged Application run configuration in Rider.
VS does work when using F5. I assumed this might be because VS calls MSBuild, not the dotnet CLI, but after checking, I noticed that Rider calls MSBuild directly, too.
I find the Rider's bug. Rider will use .NET Framework debugger to debug the application when I select the msbuild to build the project.
Current behavior
When creating a project via the template wizard, the generated
AppHead.xaml
fails to loadAppResources.xaml
on Windows and crashes with aXamlParseException
.This seems to be a Windows issue, as running the project on Android is successful (or at least, it starts up without crashing).
Expected behavior
The template should be able to run on all platforms if the user has not changed it.
How to reproduce it (as minimally and precisely as possible)
dotnet new unoapp -o WinTest -id "com.companyname.WinTest" -pub "O=WinTest" -platforms "android" -platforms "windows" -pwa False -theme "fluent" -presentation "none" -config false -di false -log "none" -nav "blank" -http false -loc false -server false -tests "none" -toolkit false -dsp false
AppHead.g.i.cs
's unexpected exception handler with a XamlParseExceptionCannot locate resource from 'ms-appx:///WinTest/AppResources.xaml'. [Line: 12 Position: 29]