DarranRowe
commented
6 months ago That error is curious, it is also an error I do not see. Anyway, to go through the important points.
1) The projects being out of date is a known issue. The updated project templates that have .NET 8 support can be found here. You cannot build the .vsix file, but there is nothing stopping you from using these files to properly configure a new project. As an example to show this, there is a response to another bug report last month stating that the new project templates are on the way.
2) If you are using the Windows App SDK 1.5, you really shouldn't need UseRidGraph. A project that I created to test this out works perfectly fine with:
<PropertyGroup>
<OutputType>WinExe</OutputType>
<TargetFramework>net8.0-windows10.0.19041.0</TargetFramework>
<TargetPlatformMinVersion>10.0.17763.0</TargetPlatformMinVersion>
<RootNamespace>CsTest</RootNamespace>
<ApplicationManifest>app.manifest</ApplicationManifest>
<Platforms>x86;x64;ARM64</Platforms>
<RuntimeIdentifiers>win-x86;win-x64;win-arm64</RuntimeIdentifiers>
<PublishProfile>win-$(Platform).pubxml</PublishProfile>
<UseWinUI>true</UseWinUI>
<EnableMsixTooling>true</EnableMsixTooling>
<Nullable>enable</Nullable>
</PropertyGroup>If you want this to work with all frameworks, then using the method in the project templates will work.
3) The crash at XamlCheckProcessRequirements basically mean that you do not have the Windows App Runtime referenced. If your application is packaged, then you really need to provide a sample project that exhibits this behaviour since the build system should be picking up the reference from the NuGet package. If your application is unpackaged then you missed a step in the "Create your first WinUI 3 (Windows App SDK) project" link that you provided. As per step 7 in the unpackaged section, you need to set WindowsPackageType to none in the .csproj file. This will bootstrap the Windows App Runtime into the process and allow Xaml to work. There is an added annoyance here in that using WindowsPackageType set to none will break the packaging for this type of project. There are ways around it if you want the application to work seamlessly packaged or unpackaged.
wsficke
JesseCol
torum
SO X-Post: https://stackoverflow.com/questions/78317988/cannot-create-a-new-winui-3-app-and-target-net-8
Describe the bug
After creating a new WinUI 3 project using the project template, the framework version and nuget references are not current. In this state, targeting .NET 6, the app builds and runs, and you can see the clicky button screen.
The first order of business after executing any project template is to update to the latest framework and packages. With .NET 8, there are documented RID issues that are extern from this SDK. I found a workaround (UseRidGraph) on Stack Overflow to opt out of RID graph pruning, which lets the build pass.
Updating the nuget packages prior to targeting .NET 8 does not change the scenario. The error is introduced when retargeting to .NET 8, not when updating the nuget packages to current.
Build is passing with these props:
However, when you start the app, you get this error:
Steps to reproduce the bug
Expected behavior
Windows Apps should run on .NET 8. The developer experience for starting a WinUI 3 project should be world-class and free of frustrating errors and workarounds.
Screenshots
System.DllNotFoundException: 'Unable to load DLL 'Microsoft.ui.xaml.dll' or one of its dependencies: The specified module could not be found. (0x8007007E)' @ App.g.i.cs
NuGet package version
WinUI 3 - Windows App SDK 1.5.2: 1.5.240404000
Windows version
Windows 11 (22H2): Build 22621
Additional context
Windows Apps should run great on .NET 8. The developer experience for starting a WinUI 3 project should be world-class and free of frustrating errors and workarounds.
Recommend maintaining the project templates to work with latest .NET and NuGet packages out of the box.