WIP: Creating a FAKE script to publish to VS Code gallery

[forki]

Implements https://github.com/ionide/ionide-vscode-paket/issues/4

• [x] - detect where node lives
• [x] - Install VSCE
• [ ] - Login in VSCE (waitng for https://github.com/Microsoft/vscode-vsce/pull/47 - but since it's only one time thingy it can be done manually)
• [x] - Update version in package.json from ReleaseNotes.md
• [x] - Create vsix package
• [x] - push vsix to github releases
• [x] - publish to Visual Stuido Code gallery

[Krzysztof-Cieslak]

I think local npm installation (obtained by Paket from NuGet can be uesd on Windows) - https://github.com/FractalProject/Fractal.Sample/blob/master/build.fsx#L42-L45

[forki]

Awesome ;-) On Nov 19, 2015 12:13 PM, "Krzysztof Cieślak" notifications@github.com wrote:

I think local npm installation (obtained by Paket from NuGet can be uesd on Windows) - https://github.com/FractalProject/Fractal.Sample/blob/master/build.fsx#L42-L45

— Reply to this email directly or view it on GitHub https://github.com/ionide/ionide-vscode-paket/pull/5#issuecomment-158025773 .

[Krzysztof-Cieslak]

Also, preferably during deploy process I would want to publish plugin to extension gallery but also do GitHub release of packed version (using vsce package)

[forki]

[forki]

waiting for https://github.com/Microsoft/vscode-vsce/pull/47 to get merged and released ;-)

[forki]

done!

see https://github.com/ionide/ionide-vscode-paket/releases/tag/1.0.2

[forki]

This is my release.cmd (minus passwords). It's already in gitignore.

    @echo off
    cls

    .paket\paket.bootstrapper.exe
    if errorlevel 1 (
    exit /b %errorlevel%
    )

    .paket\paket.exe restore
    if errorlevel 1 (
    exit /b %errorlevel%
    )
    packages\FAKE\tools\FAKE.exe build.fsx "target=Release" "vsce-publisher=mypublisher" "vsce-token=mykey" "github-user=myuser" "github-pw=mypw"

[Krzysztof-Cieslak]

1. VSCE path is hard coded to your path, I wonder if we could use %APPDATA% to get C:\Users\Steffen\AppData\Roaming this part of VSCE path.
2. I'm not sure if InstallVSCE and loginToVSCE should part of normal release cycle - those operations have to be done only once per machine, so while it is useful to have them in build script, i would not include them in normal release path, but rater create target Setup which will just run those 2.

[forki]

1. Oups. fixed
2. Mhm these targets run for only two seconds. It makes it really convenient ;-)

[Krzysztof-Cieslak]

Well, we don't know how vsce login will behave. I think it is asking for confirmation in case of relogging.

[forki]

Yeah we can decide later. At the moment it's not in standard pipeline. On Nov 20, 2015 14:36, "Krzysztof Cieślak" notifications@github.com wrote:

Well, we don't know how vsce login will behave. I think it is asking for confirmation in case of relogging.

— Reply to this email directly or view it on GitHub https://github.com/ionide/ionide-vscode-paket/pull/5#issuecomment-158404925 .

[Krzysztof-Cieslak]

OK, so let's do this ;)