CommunityToolkit / CommunityToolkit/Tooling-Windows-Submodule
Project Heads should have launchconfig/config for selecting non-IIS project startup as default
- Dominant language
- C#
- Stars
- 55
- Forks
- 19
- Avg merge
- 40m
- Merged PRs (30d)
- 1
Description
### 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
```text
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.
Contributor guide
Assessment
This issue has not been assessed yet.