[WASM][WindowsAppSDK] Updating existing project from .NET6 to .NET7

[DierkDroth]

Hi,

I'm working my way through updating my UNO WASM+WindowsAppSDK project from .NET6 to .NET7. A few issues I ran into:

• First thing I noticed: is there a .NET7 equivalent to this?
• Next: I get deprecation warnings below. Is that expected?
• To confirm: am I now on the latest and correct UNO templates for .NET7?
• How would I create a fresh, new UNO .NET7 project (as reference)? dotnet new unoapp-winui-net6 -o MyUnoApp obviously would not do it...
• when I tried dotnet new unoapp -o MyUnoApp would it say something about 'Multi-platform app .NET6' being created, which is not what I wanted

I also tried to create a fresh, new UNO project right in VS 17.4 (latest) as per here. However, there are no UNO project templates at all in my VS

I'm at a loss a I have no way to create a fresh, new WASM + WindowsAppSDK project for .NET7 :-(

[jeromelaban]

• First thing I noticed: is there a .NET7 equivalent to this?

It's equivalent, net6 and net7 introduce no specific change. You can create a new app without issues with the visual studio extension, or by using dotnet new unoapp and choose .NET 7 as the target framework. This particular document is outdated and will be removed.

• Next: I get deprecation warnings below. Is that expected?

Just a change in dotnet's behavior, we'll adjust our docs.

• To confirm: am I now on the latest and correct UNO templates for .NET7?

Uno 4.6.x supports .NET 7.

• when I tried dotnet new unoapp -o MyUnoApp would it say something about 'Multi-platform app .NET6' being created, which is not what I wanted

The .NET 6 reference is incorrect in the sense that it's indeed a net6 app because you did not specific -f net7.0, but you can follow the docs here to get started with net7.0 and dotnet new.

[DierkDroth]

Thanks @jeromelaban. I'll update my documentation links...