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

Provide an option to install Fake.dll (portable) using Paket #1773

Closed
pkese opened this issue Jan 31, 2018 · 5 comments
Closed

Provide an option to install Fake.dll (portable) using Paket #1773

pkese opened this issue Jan 31, 2018 · 5 comments

Comments

@pkese
Copy link

pkese commented Jan 31, 2018

Description

According to instructions in #1765, I'm now trying to move to "netcore-fake", but there appears to be no migration path for Paket users:
There appears to be no way to install any sort of Paket compatible Nuget package that would distribute a Fake.dll which one could run using dotnet fake.dll.

Repro steps

Add nuget FAKE<anything> prerelease to paket.dependencies.
Run paket update && paket install

Expected behavior

Have Fake.dll available anywhere in ./packages

Actual behavior

Fake.dll nowhere to be found.

Known workarounds

Manually download fake-dotnetcore-portable.zip from https://github.com/fsharp/FAKE/releases

Related information

  • Operating system: Windows 10
  • Revision: 5.0.beta12
  • .NET Runtime, CoreCLR or Mono Version: 2.0.x
@matthid
Copy link
Member

matthid commented Jan 31, 2018

I think the dotnet-fake package should work with the paket reprotools feature?

@pkese
Copy link
Author

pkese commented Jan 31, 2018

I tried installing dotnet-fake using Paket and sure I get dotnet-fake.dll installed.
However, when trying to run it, I get

>dotnet packages\dotnet-fake\lib\netcoreapp2.0\dotnet-fake.dll

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'Argu, 
Version=3.7.0.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
   at Program.main(String[] args)

However if I manually installed and ran dotnet fake.dll from fake-dotnetcore-portable.zip, then that woudn't fail.

Do I understand correctly, that I'm suppose to create a dummy .csproj with a reference to dotnet-fake and then somehow run dotnet with a reference to that .csproj?
(I'd actually prefer not to put extra .csproj files to my root directory).

@matthid
Copy link
Member

matthid commented Feb 1, 2018

the csproj is the nuget way. paket will hopefully support cli tools soon.
/cc @enricosada @forki

@matthid
Copy link
Member

matthid commented Feb 1, 2018

Personaly I have no objections in providing just another nuget package containing everything, but it feels wrong...

@matthid
Copy link
Member

matthid commented Feb 4, 2018

I'm closing this for now, as I think the correct thing to do is to use

repotool dotnet-fake

once we have fsprojects/Paket#2938

However, like stated above I'm not against releasing just another package if after the above PR we still feel the need. The current workaround is to use curl and the portable release, a csproj file or the global fake installation.

Feel free to suggest otherwise.

@matthid matthid closed this as completed Feb 4, 2018
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