Error 'Target ""Default"" is not defined.' - but the target is there

[mapfel]

Description

followed tutorial "GETTING STARTED WITH FAKE - F# MAKE"
https://fake.build/fake-gettingstarted.html

after pasting the 2nd code block of "CLEANING THE LAST BUILD OUTPUT"
https://fake.build/fake-gettingstarted.html#Cleaning-the-last-build-output

I get the error

The last restore is still up to date. Nothing left to do.
run "Default"
Building project with version: LocalBuild
The following targets are available:
Clean
Default
Target ""Default"" is not defined. Existing targets:

• Clean
• Default
  Script reported an error:
  -> Target ""Default"" is not defined.

Related information

• Operating system: Win 10 Pro DE
• Version of FAKE (4.X, 5.X): 5.7.0 and 5.7.2 tested

[BlythMeister]

Can you please provide the command you use to call fake?

[mapfel]

fake run build.fsx
fake build

both end up with the same messages

[matthid]

@mapfel Can you please upload your script file you wrote?

[mapfel]

it is exactly that one from the tutorial
https://fake.build/fake-gettingstarted.html

[matthid]

No I think something is different (maybe whitespace?). Can you please zip and upload the folder because something is different. Also the full fake output might be helpful. For me it looks like this:

[matthid]

@mapfel From your output it looks like some quotes got added in your setup/environment . Did you add some environment variables?

[mapfel]

attached a zip, including the fake scripts, my environment and the output
fake.2107.zip

[mapfel]

your are right: it was the TARGET variable in my environment!
deleting it, and now I have a "green" output
wtf! strange
thanks guys for your efforts!!

[matthid]

@mapfel Yes sadly that is an historic artifact and still there because of backwards compat... Maybe we should warn if it is used.

[mapfel]

Yes, in case somebody tries to upgrade like me, he will run into the same situation. It was a very frustrating experience not to be able to run the Getting Started sample.
So FAKE should check the existence of that variable and display a meaningful warning. Would be nice.

[matthid]

@mapfel Thanks for reporting, next version fake will tell when it uses the target environment variable.
Note that when looking thought the code I noticed that cli arguments are preferred so fake build --target Default should have worked as well.