launch.json contents differs from vsix and dotnet new

[jeromelaban]

Current behavior

From @mobynet1 in #17733:

Another observation is the content of the launch.json and tasks.json files. When created in Visual Studio 2022, there are many tasks in tasks.json and two configurations in launch.json. These seem to be configured correctly, but the same files when created with the online wizard are incomplete.

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)

No response

Affected platforms

No response

IDE

No response

IDE version

No response

Relevant plugins

No response

Anything else we need to know?

No response

[jeromelaban]

Thanks for the report, @mobyNet. Could you provide an example of the differences you see? Could you provide the dotnet new command line that you used to create the app, and a screenshot of the right-side panel that shows the template options in Visual Studio? Thanks!

[mobynet1]

@jeromelaban I would love to except I have created about a dozen solutions from the online wizard and from within VS2022, I don't remember exactly. I have deleted all of these and am left with what I consider the perfect uno solution I have yet generated. I have developed several libp2p services in golang and had to do some heavy lifting to the launch.json and tasks.json configured correctly to perform remote debugging. I honestly cannot remember what I saw in the uno configuration that led me to believe that the online vs the visual studio 2022 versions launch and tasks were different or deficient. I just created a new solution using the online wizard and opened the solution in vs code. These files seem complete.

As you have seen in some of the issues I have reported, I was trying to see how the Uno solution was being assembled and how it functioned. I was trying everything to find the perfect elixir. I have to admit it may have been something I did in the rush to get some analysis done to determine if moving to the Uno Platform was going to be the right decision if I did elect to move away from Maui. Yesterday, I also created about a dozen solutions, changed things to make them break on purpose so I could determine the architecture and dependencies in the solution. I finally found the perfect configuration and am in the process of porting my Maui pages over to Uno. I quickly committed this working solution to GitHub so that if I break it, and I probably will, I have a working solution to fall back on.

Since I was probably full of hot air, you should go ahead and close this issue. You also commented to me about some snark I threw at your QA department, and I apologize for that. I promise to be a good working partner with your teams so that I can contribute to the Uno Platform in a constructive way to make both of our products even better!