Closed mtnrbq closed 7 years ago
This is probably because it downloads the paket.exe. So it's expected that very first call needs a little more time.
Makes sense - not seeing any 'action' until paket is downloaded was causing this impression for me. Thx.
Can you please explain how you do this? A bit of output could probably be added
Looks like before every Paket call we silently call bootstraper without printing anything to output panel https://github.com/ionide/ionide-vscode-paket/blob/master/src/paket.fs#L75
I wonder if we should go over to magic mode with the addin
Am 28.07.2017 08:18 schrieb "Krzysztof Cieślak" notifications@github.com:
Looks like before every Paket call we silently call bootstraper without printing anything to output panel https://github.com/ionide/ ionide-vscode-paket/blob/master/src/paket.fs#L75
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/ionide/ionide-vscode-paket/issues/40#issuecomment-318570323, or mute the thread https://github.com/notifications/unsubscribe-auth/AADgNA0737TsEa_Mp3owIWqCDcmExD9Fks5sSX1IgaJpZM4OmCL_ .
Fixed in 1.7.3
- we now print out bootstrapper output to standard Paket's output channel
Not sure where this issue belongs, however, in recent (post May) iterations of VSCode and Ionide, the initial launch of paket commands seems very slow - approximately 10 seconds before the Paket output console is displayed from cold. Are there settings I can enable to try to determine where the slowdown is? (I'm seeing this on all my Windows 10 machines)