![]() To see the reports, click an extension or choose More Actions > Reports. The Visual Studio Marketplace publisher management page gives you access to each extension's Acquisition Trend over time, as well as Total Acquisition counts and Ratings & Reviews. Manually, using vsce package to package the extension into the installable VSIX format and then uploading it to the Visual Studio Marketplace publisher management page: If you haven't already provided your personal access token with the vsce login command above, vsce will ask for it. You can publish an extension in two ways:Īutomatically, using vsce publish command: vsce publish Once verified, you are ready to publish an extension. In your terminal, run the following command, and when prompted, type the Personal Access Token created in the previous step: vsce login Personal Access Token for publisher '' : **************************************************** The Personal Access Token verification succeeded for the publisher ''. Verify the newly created publisher using vsce. ![]() Optionally, fill out the rest of the fields. This can be your company or brand name.īelow is an example of publisher identifier and name for the Docker extension: Name: the unique name of your publisher that will be displayed in Marketplace with your extensions.ID: the unique identifier for your publisher in Marketplace that will be used in your extension URLs.In the new page, specify the mandatory parameters for a new publisher - identifier and name ( ID and Name fields respectively): Log in with the same Microsoft account you used to create the Personal Access Token in the previous section.Ĭlick Create publisher in the pane on the left. Go to the Visual Studio Marketplace publisher management page. Every extension needs to include a publisher name in its package.json file. Copy it to the safe location, you'll need it to create a publisher.Ī publisher is an identity that can publish extensions to the Visual Studio Code Marketplace. You'll be presented with your newly created Personal Access Token. in the Scopes list, scroll to Marketplace and select Manage scope.click Show all scopes link below the Scopes section.Expiration (optional): set the desired expiration date for the token.Organization: All accessible organizations.In the Create a new personal access token modal, select the following details for the token: On the Personal Access Tokens page, select New Token: Note that the organization's name doesn't necessarily have to be same as your publisher name.įrom your organization's home page (for example: ), open the User settings dropdown menu next to your profile image and select Personal access tokens: In the following examples, the organization's name is vscode, you should use your new organization name as appropriate. ![]() Get a Personal Access Tokenįirst off, follow the documentation to create your own organization in Azure DevOps. You need to create at least one in order to publish an extension. Vsce can only publish extensions using Personal Access Tokens. This means that authentication, hosting, and management of extensions are provided through Azure DevOps. Visual Studio Code uses Azure DevOps for its Marketplace services.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |