Selecting 'WinAppSdk Unpackaged' from the targets dropdown automatically defaults to 'WinAppSdk Packaged'

[erikvilima]

Current behavior

From a newly created app using the Wizard + blank template:

Recording.2025-01-31.140013.mp4

Expected behavior

No response

How to reproduce it (as minimally and precisely as possible)

No response

Workaround

No response

Works on UWP/WinUI

None

Environment

No response

NuGet package version(s)

Uno.Sdk: 5.6.20

Affected platforms

No response

IDE

No response

IDE version

No response

Relevant plugins

No response

Anything else we need to know?

No response

[jeromelaban]

This is a known issue here: https://developercommunity.visualstudio.com/t/WinAppSDK-Unpackaged-profile-cannot-be-s/10643735

[agneszitte]

Workaround mentioned by @dr1rrb in duplicate #762:
In the project .csproj, replace:

<TargetFrameworks>net9.0-android;net9.0-ios;net9.0-maccatalyst;net9.0-windows10.0.26100;net9.0-browserwasm;net9.0-desktop</TargetFrameworks>

by

<TargetFramework>net9.0-windows10.0.26100</TargetFramework>

to be able to select WinAppSdk Unpackaged and test it, until this issue is fixed on the VS team side.

[Darsh0307]

@agneszitte @jeromelaban @dr1rrb

After replacing the target framework in .csproj as mentioned in this comment #19410 (comment)

I am able to run the app when having WinApp sdk Unpackagedas the debugging target. But there are some errors shoiwng when debugging. If we click on yes then it successfully opens the app and even the HR also works as expected. I did already opened a issue on our side for this error https://github.com/unoplatform/private/issues/652

[jeromelaban]

Indeed, this is unrelated to this specific issue. VS 17.14 may be causing additional issues.