Event banner
Visual Studio 2022 AMA
Event Ended
Tuesday, Jun 22, 2021, 09:00 AM PDTEvent details
(IMPORTANT: If you are an Outlook user, please use this link, instead of the one above, to add to your calendar for the correct time.)
We are very excited to announce a Visual Studio 2022 AMA!
An...
EricStarker
Updated Jun 23, 2021
ErikEJ
Jun 22, 2021Copper Contributor
I publish a very popular extension; https://marketplace.visualstudio.com/items?itemName=ErikEJ.SQLServerCompactSQLiteToolbox - uses the Dev 11 SDK with VS 2012 - 2019.
I am unsure how to proceed with an update/upgrade - I have some thoughts here: https://github.com/ErikEJ/SqlCeToolbox/issues/902 - any thoughts/ideas/proposals?
(There is no Initialize code)
- mkristensenJun 22, 2021
Microsoft
One strategy I've done in the past is to upload the current version to GitHub releases. Then upgrade the entire extension codebase to support only modern versions of Visual Studio. In your case that could be 2017+ or even 2019+. That means you can upgrade toand the VSSDK meta package or community toolkit. I like this strategy because it makes me able to take advantage of newer APIs such as Task Status Center and InfoBars that aren't available in the older versions. Telemetry shows that the vast majority of extension installs happens on newer versions of VS and that hardly anyone installs extensions on old versions. But by having the GitHub release, they can always download the old version if needed. - ErikEJJun 22, 2021Copper ContributorThanks, Mads. I think I will go all in, and go for Dev 17 SDK.