Tooling-Windows-Submodule icon indicating copy to clipboard operation
Tooling-Windows-Submodule copied to clipboard

Project Heads should have launchconfig/config for selecting non-IIS project startup as default

Open michael-hawker opened this issue 2 years ago • 0 comments

Describe the bug

We need to move the non-IIS config in the launchSettings.json file above the IIS one so it's selected by default in VisualStudio:

https://github.com/CommunityToolkit/Tooling-Windows-Submodule/blob/ef77ff02493232e77a7ccbc0a8e895a2dad1880a/ProjectHeads/SingleComponent/Wasm/Properties/launchSettings.json#L10-L27

Also, should update in the All Component head.

Steps to reproduce

Try running WASM with default launch.

Expected behavior

Able to more easily run WASM heads.

Screenshots

No response

Code Platform

  • [ ] UWP
  • [ ] WinAppSDK / WinUI 3
  • [X] Web Assembly (WASM)
  • [ ] Android
  • [ ] iOS
  • [ ] MacOS
  • [ ] Linux / GTK

Windows Build Number

  • [ ] Windows 10 1809 (Build 17763)
  • [ ] Windows 10 1903 (Build 18362)
  • [ ] Windows 10 1909 (Build 18363)
  • [ ] Windows 10 2004 (Build 19041)
  • [ ] Windows 10 20H2 (Build 19042)
  • [ ] Windows 10 21H1 (Build 19043)
  • [ ] Windows 11 21H2 (Build 22000)
  • [ ] Other (specify)

Other Windows Build number

No response

App minimum and target SDK version

  • [ ] Windows 10, version 1809 (Build 17763)
  • [ ] Windows 10, version 1903 (Build 18362)
  • [ ] Windows 10, version 1909 (Build 18363)
  • [ ] Windows 10, version 2004 (Build 19041)
  • [ ] Other (specify)

Other SDK version

No response

Visual Studio Version

No response

Visual Studio Build Number

No response

Device form factor

No response

Additional context

No response

Help us help you

Yes, but only if others can assist.

michael-hawker avatar Sep 26 '23 16:09 michael-hawker