madskristensen / extensionscripts Goto Github PK

Does this script work on GitHub Actions, or would it need adjustments?

Thanks!

Corresponds to madskristensen/VsixGallery#10 and madskristensen/VsixGallery#21

I've added a readmeUrl query parameter to the upload API where you can specify the URL of the readme file. It can be relative (in which case it's assumed to be on GitHub) or absolute.

I'm not sure exactly what's needed in vsix.ps1, but I imagine the Vsix-PublishToGallery function would at least need a new optional parameter that allows you to specify the URL of the readme file.

If you didn't specify a readme URL, then perhaps the script could determine the name of the branch (master, main, develop, etc.) and specify the readme URL as master/README.md or main/README.md, etc.

Thanks for your very usefull build scripts!

With the breaking changes form VS 2022, I often have to create two versions of an extension: one for VS2019 and before and one for VS2022. These share the same code and the same solution, but build with different project files and manifest files.

Currently Vsix-UpdateBuildVersion only processess the first manifest file and leaves the second one alone.

It would be nice to have all source.extension.vsixmanifest processed.

When running in a default environment, upload fails with ssl error.
see e.g. madskristensen/VsixGallery#1

Hi Mads,

Thank you for your great work bring us lots of great extensions. As you are maintaining lots of extensions, may I know how you published them to https://marketplace.visualstudio.com? I know this repo contains script to publish vsix to http://vsixgallery.com, but I had to manually upload vsix to the official marketplace finally.

Any suggestion is appreciated, thank you.

With at least minimal documentation? Please...

Here's what happens when Vsix-PushArtifacts is invoked when vsix project folder is called Something.Vsix: https://ci.appveyor.com/project/HellBrick/hellbrick-refactorings/build/1.2.4#L37

I have a partial fix that you might find useful at HellBrick@6f9d360. It doesn't fix Vsix-PublishToGallery though (which suffers from the same problem): I've found it's easier to just do Vsix-PushArtifacts -publishToGallery instead of messing with Vsix-PublishToGallery =)

I'm setting appveyor to use the version format "1.0.0.{build}" (Major.Minor.Patch.Build), which is what I'm using on my extension's manifest.

However, after the build is done the extension version is changed to the format "Major.Minor.Build"

Tried to modify the script myself, but my Powershell skills didn't help me!

Any ideas?

When installing something like trailingwhitespace, when Visual Studio 2017 is installed, results in the following:

This is due to the fact that the Install-ChocolateyVsixPackage cmdlet isn't able to detect the currently installed version of Visual Studio.

There is a Visual Studio Chocolatey Extension package that has an API compatible cmdlet that handles the additional work that is required to make this installation work:

https://chocolatey.org/packages/chocolatey-visualstudio.extension

Namely, the Install-VisualStudioVsixExtension cmdlet.

I am working on a PR to update the Extension Script to use this cmdlet instead of the one that is currently being used.