Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

VS2022 Support #9

Closed
nanangp opened this issue Jun 22, 2021 · 4 comments
Closed

VS2022 Support #9

nanangp opened this issue Jun 22, 2021 · 4 comments
Labels
enhancement New feature or request

Comments

@nanangp
Copy link
Owner

nanangp commented Jun 22, 2021 •
edited
Loading

Gonna be interesting with all the major incoming changes .

Also note the breaking API changes.
@nanangp nanangp added the enhancement New feature or request label Jun 22, 2021
@blackboxlogic
Copy link

Would you like help with this?

@nanangp
Copy link
Owner Author

nanangp commented Nov 30, 2021

Thanks, I've got a build running locally. A couple editors have different guids, but otherwise seems to be stable.

Could use a hand to come up with a single vsix that would work in, say, 2015-2022 without having to publish two separate extensions in the marketplace. Managed to get one to build & install, but the pre-2022 instances got into dll dependency hell when invoked. Didn't try very hard, so maybe I just missed something obvious.

@blackboxlogic
Copy link

blackboxlogic commented Nov 30, 2021 •
edited
Loading

Regarding "a single vsix", this conversation might help: mayerwin/vs-customize-window-title#64
Also related:

nanangp added a commit that referenced this issue Dec 1, 2021
@nanangp
Builds on 2022, runs on 2017-2022. (issue #9)
b8c9ccc 
* Inherits from AsyncPackage (i.e. dropping support for versions below 2017/15.0).
* Depends on Microsoft.VisualStudio.SDK v15.
* Changed DTE service to DTE2 as some of the methods we require don't exist in DTE anymore.
* Some new editor GUIDs.
@nanangp
Copy link
Owner Author

nanangp commented Dec 1, 2021 •
edited
Loading

Release 2.2 up on marketplace.

@blackboxlogic Cheers for the hints. Got it working by referencing Microsoft.VisualStudio.Sdk v15 and the dependencies that it brings (mentioned in one of them).

This also means saying goodbye to VS2015 (v14) and earlier. Oh well.. Anyone on VS2012-2015 - I love you, but maybe it's time to upgrade?

@nanangp nanangp closed this as completed Dec 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nanangp @blackboxlogic