[Docs] Example Publish to Marketplace

[AlexHedley]

Is it worth adding a WIKI with steps to do things?

If you upload a release then publish it:

name: Publish

on:
  release:
    types:
      - released

jobs:
  main:
    runs-on: windows-latest

    steps:
      - uses: actions/checkout@v2
      
      - name: Download Assets
        uses: i3h/download-release-asset@v1.2.0
        with:
          owner: ${{ github.event.repository.owner.login }}
          repo: ${{ github.event.repository.name }}
          tag: ${{ github.event.release.tag_name }}
          file: EXTNAME.vsix
          token: ${{ secrets.GITHUB_TOKEN }}

      - name: Script
        run: |
          # Find VsixPublisher
          $Installation = & "${env:ProgramFiles(x86)}\Microsoft Visual Studio\Installer\vswhere.exe" -latest -format json | ConvertFrom-Json
          $Path = $Installation.installationPath
          Write-Host $Path
          $VsixPublisher = Join-Path -Path $Path -ChildPath "VSSDK\VisualStudioIntegration\Tools\Bin\VsixPublisher.exe" -Resolve
          & $VsixPublisher publish -payload ".\ EXTNAME.vsix" -publishManifest ".\build\extension-manifest.json" -personalAccessToken $env:PersonalAccessToken -ignoreWarnings "VSIXValidatorWarning01,VSIXValidatorWarning02,VSIXValidatorWarning08"
        env:
          PersonalAccessToken: ${{ secrets.PERSONAL_ACCESS_TOKEN }}

[madskristensen]

I think it would be a great thing to have a GitHub Actions example on how to publish a VSIX to the Marketplace. Not sure it belongs on this project, but it sure belongs somewhere because that is great info that people ask for all the time.

[AlexHedley]

From the discussion on the stream I did wonder if this was to go to a custom org we could create a separate docs repo (docfx) and build some useful articles like this?

Have a community set of posts, best practices etc.

Maybe transcribe your streams with some of the examples?

[madskristensen]

I love the idea of having a community driven wiki somewhere. It's almost as if we need a community org on GitHub to hold all this content. Or perhaps Microsoft can create an official one for the community to use (not sure this is possible). @leslierichardson95 what do you think?

[AlexHedley]

It's worked well with the Xamarin Community Toolkit and outside contributions, but that was an official project so not sure if this would need to be handled differently.

[yannduran]

@madskristensen anyone can create an organisation on Github, and you can add whatever GitHub accounts you like to administer it, or contribute to it, or even allow all developers to add to it.

I created one ages ago for Luminous Software. I'm not suggesting we use that particular org, just saying it's easy to create one. I could even create one for you called Visual Studio SDK Toolkit (or whatever we end up deciding to call the NuGet package etc).

Maybe transcribe your streams with some of the examples?

I wasn't planning on transcribing whole episodes, but I already had the idea of a series of blog posts that captured the excellent nuggets of information found in your Writing Extensions With Mads (phuut, that's me!) series. I just haven't started it yet. I wanted to do it for mainly for myself, but I was planning on surprising everyone by sharing the blog series url with everyone. But a wiki would also work.

[leslierichardson95]

@madskristensen I think it's a good idea to have a community wiki. I started a GitHub repo called VSExtensibility where it might fit in the long run but it's currently private at the moment for select partners given our upcoming VS updates.