fsharp/FAKE

FAKE - F# Make

mecusorin

@mecusorin_twitter

@vilinski this is a paket message, nothing to do with fake. Try again in fsprojects/Paket gitter channel

mecusorin

@mecusorin_twitter

@vilinski most probably, Paket doesn't recognize the net5.0 from the restrictions tokens

mecusorin

@mecusorin_twitter

@vilinski You can start from here: https://github.com/fsprojects/Paket/blob/9cbc7a05fc851611e541051d8f07beb8d25e9596/tests/Paket.Tests/Lockfile/ParserSpecs.fs#L796 then https://github.com/fsprojects/Paket/blob/9cbc7a05fc851611e541051d8f07beb8d25e9596/tests/Paket.Tests/Lockfile/ParserSpecs.fs#L801 find the parser and see what is doing

Andreas Vilinski

@vilinski

thank you
yes, the problem is surely related to net5.0. But the installed paket tool has no problem with producing and parsing paket.lock file.
can it be fake-cli uses own, older paket version, different from installed one?
latest alpha of fake-cli did it, don't know why

Return null

@VoidAsync_twitter

It looks like Fake is referencing Paket 5.251, I think Paket 6 is needed for .net5 support

But I could be wrong - Paket 5.250 release notes say allow net5.0 moniker

Return null

@VoidAsync_twitter

But I am seeing similar issues as Andreas. Dotnet Paket tool works fine, but seeing crash from Paket.Lockfile.Parse being called from Fake.Runtime\FakeRuntime.fs

Florian Verdonck

@nojaf

How does <== work again for targets?

Cody Johnson

@Shmew

It defines the list of targets as needing to run before the target to the left

Florian Verdonck

@nojaf

Gotcha, thanks

Justin Wick

@JustinWick

@VoidAsync_twitter: I'm likewise having problems with fake, and it's referencing an old paket, despite the fact that I'm using paket 6.0-beta1.

I even tried upgrading to the latest fake alpha, that did not fix it.

Justin Wick

@JustinWick

I upgraded my project to use net5.0. When I run dotnet fake --version:
FAKE 5 - F# Make (5.20.4-alpha.1642+vsts.cc9c2d6e6d38fde57081cbefcd940f247425f904)
Paket.Core: 5.251.0

When I run dotnet fake build:
\build.fsx (8,5)-(8,9): Error FS0039: The namespace or module 'Fake' is not defined."

Also more errors about 'Farmer' is not defined, 'Target' is not defined, 'Path' is not defined, etc...

I'm using the SAFE Stack Template from here:
https://github.com/SAFE-Stack/SAFE-template

Is it missing some kind of assembly reference I need for 5.0? I changed my paket.dependencies to have group Build use framework "net5.0", maybe that's a mistake?

Ah, that seems to be the issue, Fake doesn't want to run in net5.0 yet, changing it back to netstandard2.0 works.

Damian Reeves

@DamianReeves

Is this still the correct area to ask questions about Fake? No activity since November seems strange

Balinth

@Balinth

This is just not such a widely used tool (which is a shame) that there is always discussion. If you look back, there was a similiar jump from july to october.

Daniel Blendea

@bdaniel7

Hi,
I'm trying to pass the version parameter to DotNet.publish, like

|> DotNet.publish (fun p ->
{ p with
OutputPath = Some publishPath
MSBuildParams = { p.MSBuildParams with
Properties = [ "/p:Version" version ]
}
Configuration = DotNet.BuildConfiguration.fromString "Release" })

but I get an error.

Daniel Blendea

@bdaniel7

Is there a way to send the version to the publish target?

Balinth

@Balinth

Well what is the error? at first sight Properties = [ "/p:Version" version ] is kind of suspect, aren't you missing a comma (meaning one item that is a tuple) or a semi colon (meaning two items)?

seanamosw

@seanamosw

@bdaniel7 Try

    "ProjectPath"
    |> DotNet.publish (fun p ->
        { p with
            OutputPath = Some "OutputPath" }
        |> DotNet.Options.withAdditionalArgs [ "-p:Version=1.0.0" ])

gsuuon

@gsuuon:matrix.org

[m]

Is there any way to get fake to be less noisy? I've passed in quiet verbosity settings to the task, and set a custom trace listener but I still get the command the task executes outputted. Is it possible to just see when a task is ran and if there are errors?

Balinth

@Balinth

@gsuuon:matrix.org you could add the commands as secrets

nexaddo

@nexaddo

Quck question, I'm migrating to Fake 5 and have some common fsx scripts that are declared as modules. For the Fake Modules that are used in those common fsx files, do I need a #r "paket: ... //" header in each fsx, or just all the required modules in the main build.fsx?

Gauthier Segay

@smoothdeveloper

Unsupported log file format. Latest supported version is 9, the log file has version 13.

anyone hitting this after updating to latest VS 16.10?

Gauthier Segay

@smoothdeveloper

DisableInternalBinLog = true work around this issue

nexaddo

@nexaddo

I'm having problems with docopt
In build.cmd I have:

dotnet fake run build.fsx -t "%*"

Calling it like:

.\build.cmd Test --tier=an-dev --clientId=guid --key=<secret> --subscriptionId=guid --output

In my build.fsx I have:

let cli = """
usage: prog [options]

options:
    --tier=TIER                           environment to build against [default: an-dev]
    --config=CONFIG                       dotnet Debug build configuration
    --artifact-resource-group-name=NAME   azure resource group to use for ARM deployment
    --artifact-storage-account-name=NAME  azure storage account to use for ARM templates
    --clientId=ID                         azure jenkins service principal id
    --key=KEY                             azure jenkins service principal secret
    --subscriptionId=ID                   azure subscription id
    --tenantId=ID                         azure AD tenant id
    --no-sass-token                       don't use sass token for ARM deployment
    --gen-reports                         generate coverage report
    --output                              print ARM template output
"""

I can't get it to work with a target and use docopt

What am I missing here?

David Cumps

@CumpsD

will 5.20.5-alpha make it on NuGet? :)

since the one on nuget doesnt work with net6.0

Where communities thrive

People

Repo info

Activity