norachuga (Community Member) asked a question.
When will Visual Studio 2019 integration be supported?
Is there any plan or timeline on this? VS2019 has been out for 2 months already.
- norachuga (Community Member)
I was actually able to reverse-engineer the existing VS extension for VS2019, so this should be a very easy ask. It took only about a minute or two to add support.
All I had to do was unzip the VSIX, change the InstallationTarget and Prerequisite fields in the manifest to include the new VS version number, and rezip.
Expand Post- norachuga (Community Member)
Since Customer Experience wants to share this with other Veracode users as a workaround, here is a step-by-step guide.
This process simply extends the installation target to include VS2019, and changes the dependencies acceptable versions from being capped at VS2017 to being open-ended (per Microsoft's own VS2019 extension upgrade guides).
- Download the existing extension from the Marketplace.
- Rename the file:
- From: Veracode.VisualStudio.Extension.vsix
- To: Veracode.VisualStudio.Extension.zip
- Unzip the renamed file. Inside the extracted contents, you will be editing 3 different files.
- You may find it helpful to use a formatter to pretty-print the JSON files, as they will have been condensed to a single line. It is not necessary to flatten the JSON back after finishing.
- Open catalog.json in a text editor.
- Locate the section "packages" > "dependencies".
- There are 3 elements in this section. We will be changing the values of the last 2.
- Change the value of the 2nd element:
- From: "Microsoft.VisualStudio.Component.Roslyn.LanguageServices": "[15.0.26208.0,16.0)",
- To: "Microsoft.VisualStudio.Component.Roslyn.LanguageServices": "[15.0.26208.0,)",
- Change the value of the 3rd element:
- From: "Microsoft.VisualStudio.Component.CoreEditor": "[15.0.26208.0,16.0)"
- Save and close the file.
- To: "Microsoft.VisualStudio.Component.CoreEditor": "[15.0.26208.0,)"
- From: "Microsoft.VisualStudio.Component.CoreEditor": "[15.0.26208.0,16.0)"
- Open manifest.json in a text editor.
- Locate the section "dependencies".
- There are 2 elements in this section. We will be changing the values of both.
- Change the value of the 1st element:
- From: "Microsoft.VisualStudio.Component.Roslyn.LanguageServices": "[15.0.26208.0,16.0)",
- To: "Microsoft.VisualStudio.Component.Roslyn.LanguageServices": "[15.0.26208.0,)",
- Change the value of the 2nd element:
- From: "Microsoft.VisualStudio.Component.CoreEditor": "[15.0.26208.0,16.0)"
- To: "Microsoft.VisualStudio.Component.CoreEditor": "[15.0.26208.0,)"
- Save and close the file.
- Open extension.vsixmanifest in a text editor.
- Locate the section PackageManifest > Installation > InstallationTarget
- Change the Version value on the InstallationTarget element:
- From: <InstallationTarget Id="Microsoft.VisualStudio.Pro" Version="[11.0, 15.0]" />
- To: <InstallationTarget Id="Microsoft.VisualStudio.Pro" Version="[11.0, 17.0]" />
- Change the Version value on the InstallationTarget element:
- Locate the section PackageManifest > Prerequisites
- Change the Version value of the 1st element:
- From: <Prerequisite Id="Microsoft.VisualStudio.Component.Roslyn.LanguageServices" Version="[15.0.26208.0,16.0)" DisplayName="C# and Visual Basic" />
- To: <Prerequisite Id="Microsoft.VisualStudio.Component.Roslyn.LanguageServices" Version="[15.0.26208.0,)" DisplayName="C# and Visual Basic" />
- Change the Version value of the 2nd element:
- From: <Prerequisite Id="Microsoft.VisualStudio.Component.CoreEditor" Version="[15.0.26208.0,16.0)" DisplayName="Visual Studio core editor" />
- To: <Prerequisite Id="Microsoft.VisualStudio.Component.CoreEditor" Version="[15.0.26208.0,)" DisplayName="Visual Studio core editor" />
- Change the Version value of the 1st element:
- Save and close the file.
- Locate the section PackageManifest > Installation > InstallationTarget
- In Windows Explorer, highlight the entire contents of the Veracode.VisualStudio.Extension folder.
- Right-click the selection and choose Send To > Compressed (zipped) folder.
- This will produce a zip file. Rename the zip file to: Veracode.VisualStudio.Extension.vsix.
- You can now double-click the VSIX file and install the extension into Visual Studio 2019.
Expand Post
- Shuning, Veracode Community Manager (Veracode)
Hi @norachuga (Community Member) - thank you for sharing your findings! I am going to forward your post to the @Integrations Group as I believe this will benefit many folks in the group!
- Shuning, Veracode Community Manager (Veracode)
@norachuga (Community Member) and everyone who's been waiting for VS 2019 - the wait is over 🙂 the extension can now be downloaded in the (Deleted Group) group . Navigate to the right of the group page, you will find the "Files" corner where the extension and document are posted.
Thank you @norachuga (Community Member) again for sharing the workaround you found - it has benefited so many customers over the summer while the Veracode Team is working on the official extension. Strong effort!!
Expand Post
.png){kind=logo}
Since Customer Experience wants to share this with other Veracode users as a workaround, here is a step-by-step guide.
This process simply extends the installation target to include VS2019, and changes the dependencies acceptable versions from being capped at VS2017 to being open-ended (per Microsoft's own VS2019 extension upgrade guides).