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.

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

Visual Studio 2022 support #11

Open
wants to merge 11 commits into
base: master
Choose a base branch
from
Open

Conversation

Intrets
Copy link

@Intrets Intrets commented Nov 10, 2021

I started with an empty VSIX project and added TabGroupJump.cs. Had to add a reference to Microsoft.VisualStudio.Platform.WindowManagement, but nothing else. Building might not work for everyone (?).

As a result some files also didn't get generated in a new project, I don't think they are needed so I left them out.

@Intrets Intrets mentioned this pull request Nov 10, 2021
@Intrets
Copy link
Author

Intrets commented Nov 10, 2021

I just realised I really bruteforced it and it will ONLY work for 2022, not add support for 2022.

@Intrets Intrets closed this Nov 10, 2021
@zastrowm
Copy link
Owner

I'm okay with only having 2022 support; uploading as different extension is one possibly, which is the path I'll most likely if needed.

I need to update from preview to 2022 and check this out locally. But if it works out, I should be able to upload within the next week or so.

@zastrowm zastrowm reopened this Nov 21, 2021
@Intrets
Copy link
Author

Intrets commented Nov 22, 2021

I don't think the things I did have made much sense. On second look it is screaming piles of warnings at me about referencing local .dlls. added old VSPackage.resx back
And then there was something with a refernce to Microsoft.VisualStudio.Platform.WindowManagement that I solved by giving it a hint to the default VS2022 installation location, which of course is not good either. should be fixed

-Added back old VSPackage.resx
-Removed Microsoft.VisualStudio.Platform.WindowManagement dependency - it was only used for WindowFrame.onScreen and the IVsWindowScreen interface checks that for a WindowFrame object.
@Intrets
Copy link
Author

Intrets commented Nov 22, 2021

On the topic of uploading as a different extension, all the plugins I use have appeared as a seperate plugin for VS2022, so that will probably be necessary.
But breaking old targets like I did is maybe a bit unnecessary.

@jonas-lomholdt
Copy link

jonas-lomholdt commented Dec 23, 2021

I would love to get this thing uploaded! It's crazy there's no native support for this in VS2022 😄
If I can help in some way, I'm up for that.

@jagt
Copy link

jagt commented Jan 15, 2022

I just realized that I can just download this repo and build the extension and use it.
So here's my local build. It works on my box 😉

https://github.com/jagt/vs-NavigateTabGroups/releases/tag/vs2022

Also thanks for all your good works! I literally can't use VS without this extension.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants