-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Create a solution
alias for the existing sln
command
#40817
Comments
Hi @baronfel I am new to Open-Source Can i work on this issue. |
Awesome @kunalshokeen051 - I want to check with the rest of the team to make sure we want to do this, but once we chat about it and agree I'd love to accept a PR from you! |
@kunalshokeen051 Ok, I've taken this to the team and we're all on board with the change. If you'd like to submit a PR we'd be happy to review and help get it merged. |
Why not the other way around? Instead of just adding a |
That'd be fine - there's no huge functional difference. |
@baronfel Okay then, seems simple enough! If @kunalshokeen051 still wants to do it, please confirm, otherwise I can take it up. |
|
Hi, due to this commit can we close this issue? |
We can! Thanks! |
Is your feature request related to a problem? Please describe.
We should add a
solution
alias to the existingsln
command. The current implementation of thesln
command interacts with.sln
files, but the new.slnx
file format logically supports many of the same commands. Some quick surveys suggest that most users want the currentsln
command to interact with.slnx
files, but thesln
name could present some confusion. Adding asolution
commanddotnet project
commandThe text was updated successfully, but these errors were encountered: