Integrate Chat Bots In Azure DevOps Extensions - Chat Bot Adoptions

PS C:\Users\vegit> cd D:\
PS D:\> md NewBotinExtension
PS D:\> cd NewBotinExtension
PS D:\NewBotinExtension> node -v
PS D:\NewBotinExtension> npm install -g tfx-cli
PS D:\NewBotinExtension> npm init -y
PS D:\NewBotinExtension> npm install vss-web-extension-sdk –save

Now our code is ready and the next process is to generate a VSIX extension file to publish the package in the Visual Studio Marketplace. Follow the below URL to register or enable your accounts. This activity is to get the Publisher ID and replace the manifest file.

URL: https://aka.ms/vsmarketplace-manage

If it's your first time using Visual Studio marketplace publisher, please note out your publisher ID (Eg: My Publisher ID: VegiManiteja). So replace your publisher ID in the manifest file (vss-extension.json file) as shown in the below code.

Required Attributes for Manifest File

Property	Description	Required Notes
manifest version	A number corresponding to the version of the manifest format	This should be 1.
Id	Extension identifiers	This is a string that must be unique among extensions from the same publisher. It must start with an alphabetic or numeric character and contain 'A' through 'Z', 'a' through 'z', '0' through '9', and '-' (hyphen). Example: sample-extension.
Version	A string specifying the version of an extension.	Should be in the format major.minor.patch, for example, 0.1.2 or 1.0.0. You can also add a fourth number for the following format: 0.1.2.3
name	A short, human-readable name of the extension. Limited to 200 characters.	Example: "My Bot in Extension".
publisher	The identifier of the publisher.	This identifier must match the identifier the extension is published under with your Visual Studio marketplace. i.e., Publisher ID
categories	An array of strings representing the categories your extension belongs to. At least one category must be provided and there is no limit to how many categories you may include.	Valid values: Azure Repos, Azure Boards, Azure Pipelines, Azure Test Plans, and Azure Artifacts

Before

Now, it’s time to create a VSIX file with the below command syntax using VS Code, PowerShell, Command Prompt, or Developer Command Prompt. At this time, the VS Code terminal is using that to run the TFX tool's packaging command from my extension directory.

D:\NewBotinExtension>tfx extension create

After

Now Visual Studio extension has been created and we have switched to the Visual Studio marketplace publisher to publish our extension (.vsix file).

Click on the ‘Azure DevOps’ option to upload your.VSIX file.

Click or Drag and Drop your extension.VSIX file. Once your file is uploaded click on the ‘Upload’ button as shown in the below screenshot.

Now our extension has been uploaded and it shows a success symbol in the Version column as shown in the below screenshot.

Now click on the ‘ …’ symbol for extension options and click on ‘View Extension’ for your extension details.

Now your extension details will be visible as shown in the below screenshot.

Now it’s time to give your extension access to your organization. Now click the ‘…’ symbol and click on the ‘Share/Unshare’ options as shown in the below screenshot.

Now Click on the ‘+ Organization’ option to add your Azure DevOps Organization details as shown in the below screenshot.

Now switch to your dev.azure.com and select your organization as shown below screenshot. Click on the ‘Organization settings’ options to enable your extension.

Now Click on the ‘Extensions’ options and go to the ‘Shared’ option and click on the ‘Install’ button. Make sure this extension will be available only to your current organization.

Select your Azure DevOps Organization from the dropdown shown in the below screenshot and click on the ‘Install’ button.

Now our new extension has been enabled as shown in the below screenshot.

Now Click on the ‘My AI Bot’ option in the Repos option, you can give any name for your extension and make sure there is scope to develop extensions for Boards, Repose, Pipelines, Test Plans & Artifacts.

Now we can achieve this new idea by adopting Microsoft AI chatbots on our extensions like Azure DevOps, Visual Studio SDK, Visual Studio Code, etc.

Happy Chatting with AI Bots