How do I produce the same VSIX as the version from the store?
See original GitHub issueHello,
Currently I’m trying to make some changes to the Powershell script, but if I build the Visual Studio solution it appears to produce a different version of clang-build.ps1
. From what I can tell some scripts are merged. Is it documented somewhere how to produce the VSIX from the store?
Thanks,
Duncan
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
How can I generate the same VSIX file as the one in ...
> npm install -g vsce # Perform the next steps in the vscode-python folder. > npm ci > python3 -m pip --disable-pip-version-check install...
Read more >Anatomy of a VSIX Package - Visual Studio (Windows)
During installation, Extensions and Updates looks for the contents of the VSIX package in a folder under %LocalAppData%\Microsoft\VisualStudio\ ...
Read more >Update a Visual Studio extension for Visual Studio 2022
Developers need to use the version of the VSIX installer that comes with Visual Studio 2022 to install extensions to that version of...
Read more >How do I install a VSIX file in Visual Studio?
zip, extract it to a folder and move it to \AppData\Local\Microsoft\VisualStudio\"X.X"\Extensions where "X.X" is your VS version. Share.
Read more >Publishing Extensions
To create a publisher: Go to the Visual Studio Marketplace publisher management page. Log in with the same Microsoft account you used to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi,
I’m afraid the steps for building the VSIX package are not documented on GitHub. You will need VS2017 for that (with VS Extensibility SDK component)
Fixed in #347