-
Notifications
You must be signed in to change notification settings - Fork 8
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
dotnet - set current solution/project #6
Comments
I don't have the need for myself but I can see why you would need it though. |
Yeah I've been thinking about it and I would change maybe too many things of how the package currently works. You might see a PR coming from my end at some point in the future, when I get the time. |
There is no way to set the solution? It asks every time I dotnet-build, it asks for a solution file. Can this be a parameter to the call, maybe, so that I can define my own function? |
I stopped using You can find it here: https://github.com/sebasmonia/sharper |
In the last few days I've using dotnet in a multi-project repo.
I've found myself using the prefix args submitted in my last pull request. Also in my local dotnet.el I added more variables to keep track of the last project for
build
,run
, etc. At this rate each function will have it's own variable!!!I think it would be convenient to have a way to setup a default project so that all commands use it, and allow overrides with
C-u
.Sample workflow:
C-u
prefixI think most commands could share the same default, except
dotnet-run
: build, add reference, etc can work on a whole solution but you usually run only one project within the solution directories.So in essence we would need 2 variables to track the "current project".
I also think it would be great to show the current projects in the echo area when the dotnet-mode keymap is active, if possible, so you know that you need to add an arg to your call.
This adds some complexity to the package, though, and changes it's behaviour quite a bit. So unless you see an use for these changes yourself, I can keep these in my own branch (when I get around to making them hehe)
The text was updated successfully, but these errors were encountered: