Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Getting started needs some clarification

See original GitHub issue

Description

Getting started states in step 5:

After the first .paket/paket.exe invocation Paket will create a couple of files in .paket — commit those as well.

Without any parameters that throw:

Paket version 5.201.1
no valid subcommand has been specified.

Repro steps

Follow steps as described in Getting started
run the provided statement

Expected behavior

creation of some assets as described in the documentation

Actual behavior

output no valid subcommand has been specified
nothing else

Known workarounds

no workaround known

Issue Analytics

State:
Created 4 years ago
Comments:6 (4 by maintainers)

Top GitHub Comments

1reaction

mapfelcommented, May 4, 2019

Yes, one of these subcommands will work depending upon the current starting point. But for a Getting Started tutorial it should provide a working subcommand.

During the first steps with Paket you don’t have a clue what’s going on and you like to get a first impression. Running into an error during your first steps creates frustrations, which often enough let you stop from going deeper into a topic. The first impression counts.

1reaction

agrosscommented, May 3, 2019

paket init or convert-from-nuget or auto-restore --on are the usual suspects.

On Fri, May 3, 2019, 20:41 Peter Kremsner notifications@github.com wrote:

What is the first .paket/packet.exe invocation at that point?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/fsprojects/Paket/issues/3546#issuecomment-489199067, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAD65ILTE23RSSPPWR7H2DPTSBNXANCNFSM4HEQ2OGA .