Add support for dotnet .slnx solution files (nuget), using Microsoft.VisualStudio.SolutionPersistence

[sailro]

Note:

This is a port of an initial prototype made by @austindrenski using custom .slnx parsing. (thanks!)

Given the PR was stale for several weeks, I created this new one, following suggestions made by @brettfo, specifically using the official Microsoft.VisualStudio.SolutionPersistence API.

What are you trying to accomplish?

• Adds support for the new .slnx solution format, using the official Microsoft.VisualStudio.SolutionPersistence API.
• Update the existing .sln support to use this new API as well. As suggested, keep the existing code for .sln support.

Fixes: #11671

Anything you want to highlight for special attention from reviewers?

• This should solve all issues reported for the initial prototype.
• API reference: https://github.com/microsoft/vs-solutionpersistence

How will you know you've accomplished your goal?

• dependabot will work with repositories using this new file format.

Checklist

• I have run the complete test suite to ensure all tests and linters pass.
• I have thoroughly tested my code changes to ensure they work as expected, including adding additional tests for new functionality.
• I have written clear and descriptive commit messages.
• I have provided a detailed description of the changes in the pull request, including the problem it addresses, how it fixes the problem, and any relevant details about the implementation.
• I have ensured that the code is well-documented and easy to understand.

[sailro]

cc @baronfel for awareness

[baronfel]

Love it!

[sailro]

cc @brettfo for awareness given he reviewed the initial prototype made by @austindrenski

[austindrenski]

Amazing work @sailro!

Appreciate you taking up #11694 and running with it! (Tale as old as time: find an interesting self-contained task, open a shiny new PR for it, work gets crazy, shiny new PR languishes growing ever staler. A modern day tragedy, but also, an unavoidable cannon event, lol).

I'm going to close #11694 as using the official upstream parsing library is undeniably a more robust solution (no pun intended), less likely to break over time, etc.!

🚢🚢🚢🚢🚢

[brettfo]

PR looks good, thank you!

I see there are some conflicts. As soon as those are resolved ping me again (I get lots of GitHub notifications so directly mentioning me is your best bet) I'll re-approve to make the CI checks happy.

[sailro]

PR looks good, thank you!

I see there are some conflicts. As soon as those are resolved ping me again (I get lots of GitHub notifications so directly mentioning me is your best bet) I'll re-approve to make the CI checks happy.

Thank you @brettfo, we should be good now.