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

dotnet new fake does not create paket.dependencies #2486

Closed
MarneeDear opened this issue Mar 14, 2020 · 4 comments · Fixed by #2520
Closed

dotnet new fake does not create paket.dependencies #2486

MarneeDear opened this issue Mar 14, 2020 · 4 comments · Fixed by #2520

Comments

@MarneeDear
Copy link

Description

Following the instructions here: https://fake.build/fake-template.html#Fake-Template

This will create a default build.fsx file, a paket.dependencies file used to mangage your build dependencies and two shell scripts fake.sh and fake.cmd.

It does create some of them but not paket.dependencies.

Also, I am prompted to update to latest version for some reason.

I had installed fake as a global tool previously like this:

dotnet tool install fake-cli -g

Repro steps

  1. Start with a solution that does not have any fake scripts or paket.dependencies.
  2. dotnet new fake
  3. Some files are created but not paket.dependencies

Expected behavior

This will create a default build.fsx file, a paket.dependencies file used to mangage your build dependencies and two shell scripts fake.sh and fake.cmd.

Actual behavior

$ dotnet new fake
The template "FAKE - Template" was created successfully.

Processing post-creation actions...
Template is configured to run the following action:
Description: update to latest version
Manual instructions: Run 'dotnet tool update fake-cli'
Actual command: dotnet tool update fake-cli
Do you want to run this action (Y|N)?
y
Running command 'dotnet tool update fake-cli'...
Command succeeded.

$ dir
 Volume in drive C is SSD
 Volume Serial Number is 26E4-5300

 Directory of C:\blahblahfishcakes

03/14/2020  12:49 PM    <DIR>          .
03/14/2020  12:49 PM    <DIR>          ..
03/14/2020  12:49 PM    <DIR>          .config
05/18/2019  04:59 PM             6,371 .gitignore
12/26/2019  08:49 AM    <DIR>          .ionide
10/26/2019  10:40 AM    <DIR>          .vs
10/26/2019  09:06 AM    <DIR>          .vscode
10/26/2019  09:06 AM    <DIR>          blog
03/14/2020  12:49 PM               608 build.fsx
10/26/2019  09:15 AM             9,787 chickadee.sln
10/26/2019  09:06 AM    <DIR>          database
02/23/2019  06:37 PM               113 Dockerfile
03/14/2020  12:49 PM                35 fake.cmd
03/14/2020  12:49 PM                82 fake.sh
03/14/2020  09:31 AM                47 global.json
10/26/2019  09:41 AM             1,101 LICENSE
10/26/2019  09:37 AM             4,941 logo.png
10/26/2019  10:11 AM    <DIR>          publish
10/26/2019  10:39 AM            12,158 README.md
08/31/2019  07:58 PM    <DIR>          REC
10/26/2019  09:06 AM    <DIR>          reference-materials
10/26/2019  09:11 AM    <DIR>          src
02/24/2019  09:32 AM    <DIR>          static
09/02/2019  08:07 AM    <DIR>          XMIT
10/26/2019  09:06 AM    <DIR>          XMITtest

Check the files that are created and see that paket.dependencies is not created.

Known workarounds

None

Related information

  • Windows 10
  • .NET Core 3.1 SDK
$ dotnet --info
.NET Core SDK (reflecting any global.json):
 Version:   3.1.102
 Commit:    573d158fea

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.18363
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\3.1.102\

Host (useful for support):
  Version: 3.1.2
  Commit:  916b5cba26

.NET Core SDKs installed:
  1.1.13 [C:\Program Files\dotnet\sdk]
  2.1.300 [C:\Program Files\dotnet\sdk]
  2.1.403 [C:\Program Files\dotnet\sdk]
  2.1.505 [C:\Program Files\dotnet\sdk]
  2.1.509 [C:\Program Files\dotnet\sdk]
  2.1.801 [C:\Program Files\dotnet\sdk]
  2.2.101 [C:\Program Files\dotnet\sdk]
  2.2.105 [C:\Program Files\dotnet\sdk]
  3.1.100 [C:\Program Files\dotnet\sdk]
  3.1.102 [C:\Program Files\dotnet\sdk]
  • Low severity
  • Version of FAKE : 5.19.1
$ dotnet fake --version
FAKE 5 - F# Make (5.19.1) (this line is written to standard error, see https://github.com/fsharp/FAKE/issues/2066)
FakePath: C:\Users\marnee\.nuget\packages\fake-cli\5.19.1\tools\netcoreapp2.1\any\Fake.Runtime.dll
Paket.Core: 5.241.2
@github-actions
Copy link
Contributor

Welcome to the FAKE community! Thank you so much for creating your first issue and therefore improving the project!

@MarneeDear MarneeDear changed the title dotnet new fake does not create paket.dependencies dotnet new fake does not create paket.dependencies Mar 14, 2020
@matthid
Copy link
Member

matthid commented Mar 14, 2020

Yes nice catch, since 91e749a#diff-c70ec698035e2a0f90d973ae51ab96ec inline-dependencies are the default for new scripts created via the template (to make it easier for newcomers to just use FAKE and not have to learn all paket details as well)

Apparently, I failed to update the docs accordingly... So with --dependencies file you can get the template to create a new paket.dependencies file if you want.

@MarneeDear
Copy link
Author

Thanks @matthid

This command worked

dotnet new fake -d file

DavidSSL added a commit to DavidSSL/FAKE that referenced this issue Jun 6, 2020
@github-actions
Copy link
Contributor

There has not been any activity in this issue for the last 3 months so it will be closed in 14 days if there is no activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants