OutputType should be WinExe for Windows targets

[lextm]

On which page?

uno.templates/src/Uno.Templates/content/unoapp/MyExtensionsApp.1/MyExtensionsApp.1.csproj

Line 5 in f3c8675

<OutputType>Exe</OutputType>

What's wrong?

If Exe is used to publish Windows artifacts, the application runs from a console window, which isn't ideal.

Any feedback?

I am using <OutputType Condition=" '$(RuntimeIdentifier)' != '' and $(RuntimeIdentifier.StartsWith('win-')) ">WinExe</OutputType>, but wonder if that's the best solution here.

[DevTKSS]

@lextm I dont think this is correct, because the Microsoft docs are telling themselfs to use Exe and the WinExe Type would attempt to produce a WPF or WinForms App, no WinAppSdk like or UWP like app on desktop:
https://learn.microsoft.com/dotnet/core/project-sdk/msbuild-props-desktop
https://learn.microsoft.com/en-us/dotnet/standard/frameworks#how-to-specify-a-target-framework

[lextm]

@DevTKSS You can try yourself with a project like DotUninstall. Where if the WinExe line is missing from the project file, the produced Windows executable launches with the annoying console window. The Microsoft articles are not useful in this case, as they don't cover that level of details.

I didn't test all other scenarios (for instance, without SkiaRenderer) but from this tiny little project I can see that using Exe as output type is not the right approach.