search

eberthold / SteroidsVS

Visual Studio Extension
https://marketplace.visualstudio.com/items?itemName=eberthold.SteroidsVS
MIT License
25 stars 2 forks source link

0.2.44.0 is broken in vs2019 #25

Closed LaraSQP closed 3 years ago

LaraSQP commented 4 years ago

Somehow, all features of SteroidsVS have stopped working after this update (via VSIX Gallery).

I uninstalled it, then installed the previous version (0.2.43.1) from the Visual Studio Marketplace, and was able to restore it to working condition.

However, when it updates itself (via VSIX Gallery), it ceases working. So 'automatic updates' are disabled for now.

My apologies for this pathetic bug report which is not going to tell you much at all. I wish I could provide more information but this extension is a must-have (thank you very, very much) and cannot allow it to update itself to dig further into the issue.

eberthold commented 4 years ago

Hey, thanks for your feedback. I was very tired when merging my local branches and preparing the release and messed up 😴. I use vsixgallery.com as my pre-release channel to test the extension before live publish. Didn't expect it to be used by others for normal VS Extensions updates 😏 that's why i didn't push a fix right after.

Basically I have produced a bug in the dependency graph setup. Thats why the startup of the extensions fails. I will release a fix later today in both vsixgallery and, when working as expected, to vs marketplace.

LaraSQP commented 4 years ago

Much appreciated.

eberthold commented 4 years ago

FYI

I released the update to vsix gallery (0.2.44.1). I tested yesterday at work and it's working with VS2019. The release for the official channel has to wait for another fix, because support for VS 2017 was broken while fixing #22

LaraSQP commented 4 years ago

Darn.

I noticed the update to VS2017 was broken and freaked me out some. Reverted back to 0.2.43.1 as fast as I could.

Good to know you are on it.

Like I said. Your extension is a must. Good karma to you.

eberthold commented 4 years ago

Sad news, it seems like I have to drop support for VS2017. The effort to maintain multiple SDK versions - while targeting features of the latest one - is simply too high for a spare time project. I will publish a new version to both pipelines which will drop support. This will prevent broken updates for 2017 at least.

Reopening this issue if maybe someone who has some more insights to versioning for vsix projects want's to contribute.

LaraSQP commented 4 years ago

I am doing the same with my own extensions and support only VS2019.

And, no worries, 0.2.43.1 does the job fine in VS2017.

The effort is appreciated.