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

I need a strategy to install multiple dotnet versions in parallel #1640

Closed
0x53A opened this issue Aug 26, 2017 · 4 comments
Closed

I need a strategy to install multiple dotnet versions in parallel #1640

0x53A opened this issue Aug 26, 2017 · 4 comments

Comments

@0x53A
Copy link
Contributor

0x53A commented Aug 26, 2017

For fsprojects/Paket#2664 I need the 2.x Sdk and the 1.x Runtime.

The issue is that DotNetCli.InstallDotNetSDK cleans up before it installs anything - so if I first install 1.x then 2.x, 1.x will be deleted.

Instead it should (maybe only if configured, so it doesn't waste too much space) merge the two installations.

For comparison, you can take a look at the folder structure created by the MS installers:

C:\Program Files\dotnet

image

image

and so on.

There is one dotnet.exe in the root (probably the latest?), but many dirs in parallel.

@matthid
Copy link
Member

matthid commented Aug 26, 2017

In FAKE 5 that thing is replaced with https://github.com/fsharp/FAKE/tree/master/src/app/Fake.DotNet.Cli which runs the "official" install script. Maybe that could be tweaked to have the same structure or works better ootb?

@0x53A
Copy link
Contributor Author

0x53A commented Aug 26, 2017

The use-case in Paket was "fixed" by just recompiling the affected binary against netcoreapp2.0.

But I would guess that this requirement (2.x Sdk + 1.x Runtime) will be common.

Are there any reasons against either moving Paket to Fake.5, or backporting this stuff to Fake.legacy? If backported, probably with a different method name...

@matthid
Copy link
Member

matthid commented Aug 26, 2017

@0x53A no real reason, just something historical I added this in the FAKE 5 branch before someone wrote this again in the master branch :/. You can use it directly via paket-files or the nuget package

@matthid
Copy link
Member

matthid commented Oct 15, 2017

So I guess this is solved.

@matthid matthid closed this as completed Oct 15, 2017
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

No branches or pull requests

2 participants