Computer extension command, use command line release extension - Visual Studio (Windows) | Microsoft Docs

1. Visual Studio Command Line Options
2. Visual Studio Command Line Debugger

Command Line Interface (CLI) Visual Studio Code has a powerful command line interface built-in that lets you control how you launch the editor. You can open files, install extensions, change the display language, and output diagnostics through command-line options (switches). The trick is to use one of the “Command Prompt” you’ll find in the start menu: I started with the “Developer Command Prompt”: cd c: User dmerej src cmake build-vs devenv CMake.sln. Visual Studio opened. Hum, that’s not what I wanted. Turns out, if you make any mistake in the command line prompt, Visual Studio will open. Visual Studio includes a command-line C and C compiler. You can use it to create everything from basic console apps to Universal Windows Platform apps, Desktop apps, device drivers, and.NET components. In this walkthrough, you create a basic, 'Hello, World'-style C program by using a text editor, and then compile it on the command line.

tags: Computer extension command

Exercise: Publish Visual Studio expansion by command line

A command URI uses the command scheme followed by the command name. The command URI for the editor.action.addCommentLine command, for example, is command:editor.action.addCommentLine. Here's a hover provider that shows a link in the comments of the current line in the active text editor. Adds support for command line batch files in Visual Studio 2015's Task Runner Explorer. Supports.exe,.cmd,.bat,.ps1 and.psm1 files. The easiest way to add a batch file to Task Runner Explorer is to right-click it in Solution Explorer and selectAdd to Task Runner.

07/12/2018

Herein

This drill demonstrates how to use the command line to publish the Visual Studio extension to Visual Studio Marketplace. After adding an extension to Marketplace, developers can browse new and updated extensions using the Extension and Update dialog box.

Vsixpublisher.exe is a command line tool that publishes the Visual Studio extension to Marketplace. It can be accessed from $ {vsinstalldir} vssdk VisualstudioIntegration Tools BIN VSIXPUBLISHER.EXE. The commands available on this tool include: publishing, CreatePublisher, deletePublisher, deleteextension, login, logout.

Order

release

Publish the extension to MarketPlace. Extensions can be vsix, exe / msi files, or links. If there is extension with the same version, it will overwrite the extension. If the extension does not exist, a new extension will be created.

Command option

instruction

Load (required)

The path to the payload to be published or used as a link to the Details URL.

Publishmanifest (required)

The path to the published manifest file to be used.

ignoreWarnings

A list of warns to ignore when publishing an extension. These warnings are displayed as command line messages when expanding. (For example, 'vsixvalidatorWarning01, vsixvalidatorWarning02')

personalAccessToken

A personal access token for authenticating the publisher (PAT). If not provided, PAT will be obtained from the logged in user.

VsixPublisher.exe publish -payload '{path to vsix}' -publishManifest '{path to vs-publish.json}' -ignoreWarnings 'VSIXValidatorWarning01,VSIXValidatorWarning02'

createPublisher

Create a publisher on Marketplace. The publishing server will also be recorded in the computer to perform an operation (for example, delete / release extension).

Command option

instruction

DisplayName (required)

The display name of the publish server.

Publishername (required)

The name of the publish server (for example, an identifier).

PersonaCCCESSTOKEN (required)

A personal access token for authenticating the publishing server.

shortDescription

A brief description of the publish server (not) file.

longDescription

Detailed description of the publish server (not a file).

VsixPublisher.exe createPublisher -publisherName '{Publisher Name}' -displayName '{Publisher Display Name}' -personalAccessToken '{Personal Access Token}'

deletePublisher

Delete the publishing server on MarketPlace.

Command option

instruction

Publishername (required)

The name of the publish server (for example, an identifier).

PersonaCCCESSTOKEN (required)

A personal access token for authenticating the publishing server.

VsixPublisher.exe deletePublisher -publisherName '{Publisher Name}' -personalAccessToken '{Personal Access Token}'

deleteExtension

Remove extensions from MarketPlace.

Command option

instruction

ExtensionName (required)

The name of the extension to be deleted.

Publishername (required)

The name of the publish server (for example, an identifier).

personalAccessToken

A personal access token for authenticating the publishing server. If not provided, PAT will be obtained from the logged in user.

VsixPublisher.exe deleteExtension -extensionName '{Extension Name}' -publisherName '{Publisher Name}'

login

Record the publisher to your computer.

Command option

instruction

Need PersonaCCCESSTOKEN (

A personal access token for authenticating the publishing server.

Publishername (required)

The name of the publish server (for example, an identifier).

overwrite

Specifies to override any existing publishing servers using the new personal access token.

VsixPublisher.exe login -personalAccessToken '{Personal Access Token}' -publisherName '{Publisher Name}'

logout

Record the publisher outside the computer.

Command option

instruction

Publishername (required)

The name of the publish server (for example, an identifier).

ignoreMissingPublisher

If the specified publisher is not logged in, specify that the tool will not be wrong.

VsixPublisher.exe logout -publisherName '{Publisher Name}'

Publishmanifest file

The 'Publish' command uses the publishmanifest file. It indicates that MarketPlace needs to be understood about all metadata of the extended. If the extended extension is from the vsix extension, the 'Identity' property can only be set to 'internalname'. This is because you can generate the rest of the 'ID' property from the Source.extension.vsixManifest file. If the extension is MSI / EXE or link extension, the user must provide the required field in the 'Identity' property. The rest of the list contains MarketPlace (information, such as categories, Q &, etc.).

VSIX Extension PublishManifest file example:

{

'$schema': 'http://json.schemastore.org/vsix-publish',

'categories': [ 'build', 'coding' ], // The categories of the extension. Between 1 and 3 categories are required.

'identity': {

'internalName': 'MyVsixExtension' // If not specified, we try to generate the name from the display name of the extension in the vsixmanifest file.

// Required if the display name is not the actual name of the extension.

},

'overview': 'overview.md', // Path to the 'readme' file that gets uploaded to the Marketplace. Required.

'priceCategory': 'free', // Either 'free', 'trial', or 'paid'. Defaults to 'free'.

'publisher': 'MyPublisherName', // The name of the publisher. Required.

'private': false, // Specifies whether or not the extension should be public when uploaded. Defaults to false.

'qna': true, // Specifies whether or not the extension should have a Q&A section. Defaults to true.

'repo': 'https://github.com/MyPublisherName/MyVsixExtension' // Not required.

}

MSI / EXE or LINK PUBLISHMANIFEST file example:

{

'$schema': 'http://json.schemastore.org/vsix-publish',

'categories': [ 'build', 'coding' ],

'identity': {

'description': 'My extension.', // The description of the extension. Required for non-vsix extensions.

'displayName': 'My Extension', // The display name of the extension. Required for non-vsix extensions.

'icon': 'pathtoicon.ico', // The path to an icon file (can be relative to the json file location). Required for non-vsix extensions.

'installTargets': [ // The installation targets for the extension. Required for non-vsix extensions.

{

'sku': 'Microsoft.VisualStudio.Community',

'version': '[10.0, 16.0)'

}

],

'internalName': 'MyExtension',

'language': 'en-US', // The default language id of the extension. Can be in the '1033' or 'en-US' format. Required for non-vsix extensions.

'tags': [ 'tag1', 'tag2' ], // The tags for the extension. Not required.

'version': '3.7.0', // The version of the extension. Required for non-vsix extensions.

'vsixId': 'MyExtension', // The vsix id of the extension. Not required but useful for showing updates to installed extensions.

},

'overview': 'overview.md',

'priceCategory': 'free',

'publisher': 'MyPublisherName',

'private': false,

'qna': true,

'repo': 'https://github.com/MyPublisherName/MyVsixExtension'

}

Asset file

An asset file can be provided to embed images in the readme file. For example, if the extension has the following 'overview' MARKDOWN document:

TestExtension

...

This is test extension.


In order to solve 'ImageS / TestLogo.png' in the previous example, users can provide 'AssetFiles' in their publishing list, as shown below:

{

'assetFiles': [

{

'pathOnDisk': 'pathtologo.png',

'targetPath': 'images/logo.png'

}

],

// other required fields

}

Release drill

prerequisites

To follow the steps of this exercise, Visual Studio SDK must be installed. For more information, see Installing Visual Studio SDK.

Create a Visual Studio extension

In this case, we will use the default vSPackage extension, but the same steps are valid for each type of extension.

Create a VSPackage called 'TestPublish' in C #, which contains a menu command. For more information, see Creating the first extension: Hello World.

Package extension

The extended source.extension.vsixManifest is updated to the correct information about the product name, author, and version.

Build an extension in the release mode. Now, your extension will package a VSIX in the bin release folder.

You can double-click VSIX to verify the installation.

Test expansion

Before distributing extensions, generate and test the extension to ensure that it is properly installed in the experimental example of Visual Studio.

In Visual Studio, start debugging. Open the experiment example of Visual Studio.

In an experimental example, click the Tools menu, then click Extensions and Update .... TestPublish extensions should appear in the central pane and enable.

On the Tools menu, make sure you see the 'Test' command.

Publish the extension to Marketplace through the command line

Make sure that the extension release is generated, and this version is the latest version.

Make sure you have created a PublishManifest.js and an Overview.md file.

Open the command line and navigate to $ {vsinstalldir} vssdk VisualstudioIntegration Tools bin directory.

To create a new publisher, use the following command:

VsixPublisher.exe createPublisher -publisherName 'TestVSIXPublisher' -displayName 'Test VSIX Publisher' -personalAccessToken '{Personal Access Token that is used to authenticate the publisher. If not provided, the pat is acquired from the logged-in users.}'

After successfully created a publishing server, the following command line message is displayed:

Added 'Test VSIX Publisher' as a publisher on the Marketplace.

To post a new extension, use the following command:

VsixPublisher.exe publish -payload '{Path to vsix file}' -publishManifest '{path to publishManifest file}'

After successfully created a publishing server, the following command line message is displayed:

Uploaded 'MyVsixExtension' to the Marketplace.

Install extension from Visual Studio Marketplace

After the extension has been released, install in Visual Studio and test it in it.

On the Tools menu of Visual Studio, click Extensions and Updates ... '.

Click Online, then search 'TestPublish'.

Click Download. Then, the schedule will be installed.

To complete the installation, close all instances of Visual Studio.

Delete extension

This extension can be removed from Visual Studio Marketplace and your computer.

Remove the extension from MarketPlace by command line

If you want to delete an extension, use the following command:

Visual Studio Command Line Options

VsixPublisher.exe deleteExtension -publisherName 'TestVSIXPublisher' -extensionName 'MyVsixExtension'

After successfully delete the extension, you will see the following command line message:

Removed 'MyVsixExtension' from the Marketplace.

Remove extensions from your computer

Visual Studio Command Line Debugger

On the Tools menu of Visual Studio, click Extensions and Updates.

Select 'MyVsixExtension' and click Uninstall. Then, this extension will be planned for the uninstallation.

To complete uninstall, close all instances of Visual Studio.

Intelligent Recommendation

The Microsoft One-Stop Sample Code Library publishes the Visual Studio 2010 sample code search extension. The extension willOne-stop sample code browserThe functionality is integrated into Visual Stud...

It is common to use VS Studio to write C# code, but did you know that you can compile C# code from the command line? You can use the command line instead of Visual Studio IDE to compile C# programs: L...

In the demand scenario where the Visual Studio project is automatically packaged and released, you need to compile directly under the command line, find a solution on the Internet, and make a record. ...

Test cloud service performance 11/11/2016 Herein Overview The performance of the cloud service can be tested in the following ways: Using Azure diagnostics, you can collect information about requests ...

Language Server Agreement 11/14/2017 Herein What is the language server protocol? Typically, rich editing features, such as the source code of the programming language in the editor or IDE, or 't...

More Recommendation

View the code structure with different tools window 09/19/2019 Herein You can use a variety of tool windows to check classes and its members in Visual Studio, including 'Class View', 'C...

Reference address:https://blog.2ndquadrant.com/compiling-postgresql-extensions-visual-studio-windows/ Foreword This article records the use of vs for source code compilation, the compiled version is x...

Use of Windows command line Common instruction Enter a folder cd folderName Display folder directory dir Back to previous cd… Switch the current disk Switch to D disk D: Switch to C disk C: new...

In the Visual Studio2017 [Tools] menu As shown in the figure, select an external tool Create a command line execution environment Click [Add] title User-defined, will be displayed in the menu item of ...

Since installationVisual Studio 2017 After that, there was a biggest difference in the use that had been bothering me. Today I finally decided to spend ten minutes to solve it. I am used to using shor...