Remove mono / full .net from prerequisites #103
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
What if you want to manipulate dependencies e.g. add a new package to repo solution - what's the recommendation for that? |
|
Install Paket as global dotnet tool - if that does not work for someone, then bootstrap Paket the standard way |
|
actually changed the semantics to "Paket can also be installed as global tool" to communicate that it doesn't really matter - IMO bootstrapping Paket is relevantly easy, and the big advantage is we remove dependency on Mono / Full .NET in bare template |
|
@theimowski is this good to go? |
|
yes please deploy it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
IMO we should drop requirement on full .NET / mono for legacy Paket and instead suggest installing (optionally) Paket as global dotnet tool.
Optionally, because as long as you don't need to manipulate dependencies, you can build fine with just using FAKE.
This is a temporary solution until we upgrade to .net core 3.0 and use local dotnet tools