Unable to run Windows application from .NET SDK command line

[mattleibow]

Describe the bug

See more details in dotnet/maui#5975

We should be able to run a windows app with dotnet run or dotnet build -t:Run at the very least.

Steps to reproduce the bug

1. New WinUI app using net6+
2. dotnet run

Expected behavior

App launches (for both packaged and unpackaged)

Screenshots

No response

NuGet package version

1.1.4

Packaging type

No response

Windows version

No response

IDE

Other

Additional context

No response

[DrusTheAxe]

There are ways to launch packaged apps from the command line. See dotnet/maui#5975 (comment)

If you're looking to run dotnet.exe and have it launch your app (and that doesn't happen today) that's a .NET issue you should discuss further with the .NET team (e.g. via that MAUI issue thread). Windows has APIs to programmatically launch packaged apps but it would be up to dotnet.exe to call them.

[gabbybilka]

Did @DrusTheAxe's suggestion resolve this issue?

[mattleibow]

The first step might be to follow several other workloads and make a "Run" target that the dotnet run CLI can use. Having the core sdk know about all the different permutations of different apps might not be that feasable.

So having each framework do the thing, and the core SDK just execute it is probably better - and run may also need a build so a Run depends on Build is super easy.

But as of today, we have nothing. So a Run target is going to be very helpful.

[AvtsVivek]

I think the issue I raised here on SO is similar.

[mattleibow]

It appears if you build and then run an unpackaged app it works a bit better: dotnet/maui#13942