Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Use new parser from vs-solutionpersistence to later enable .slnx support #644

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

mruxmohan4
Copy link
Contributor

Kept as draft for ease of review.

@mruxmohan4 mruxmohan4 force-pushed the dev/mruxmohan/slnx branch 7 times, most recently from 8f9f182 to d4f1f1b Compare January 9, 2025 10:47
Directory.Packages.props Outdated Show resolved Hide resolved
Directory.Packages.props Outdated Show resolved Hide resolved
@kasperk81
Copy link

slngen's command line options are

  -d|--solutiondir <path>             An optional path to the directory in which the solution file will be generated. Defaults to the same directory as the project. --solutionfile will take precedence over this switch.
  -o|--solutionfile <path>            An optional path to the solution file to generate. Defaults to the same directory as the project.

consider adding --format <sln|slnx>

upcoming dotnet SDK 9.0.2xx (and v10 from daily builds) has

dotnet new sln --help
...
Template options:
  -f, --format <sln|slnx>  Choose the format for the solution file: sln or slnx.
                           Type: choice
                             sln   Solution file
                             slnx  XML Solution file
                           Default: sln

see the feedback from VS team about naming/terminology dotnet/sdk#44469 (comment)

@mruxmohan4 mruxmohan4 force-pushed the dev/mruxmohan/slnx branch 2 times, most recently from 1d120a3 to ef42fb3 Compare January 21, 2025 20:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants