Fails to launch on 2022 17.2.0 Preview 5.0

From ActivityLog.xml:

SetSite failed for package [BuildVisionPackage]
Source: 'Microsoft.VisualStudio.Validation'
Description: Cannot find an instance of the Microsoft.VisualStudio.Shell.Interop.IVsSolutionBuildManager5 service.

VS otherwise works fine, so particular error is a bit puzzling. Perhaps the extension is loaded too early?

[StefanKert]

Hi folks,

so first of all, I am very sorry for all the inconveniences and troubles that the extension has caused in the new VS update. As of private reasons I did not have a lot of time in the last months to focus enough on BuildVision and the changes that have been introduced in VS 2022 hit the extension pretty hard. There have been some under the hood changes that will probably require to have a completely new version of BuildVision (very correct there @Mostlypyjamas 😃). Currently the biggest blocking part is retrieving events for updates of the solution (as @chucker pointed out there is a missing package). As the version in the branch that has mentioned by @michael-hawker was already working in VS 2022 I guess there have been even more changes that make it impossible to work with VS 2022 now… sorry for that.

I actually was hoping that Microsoft would improve the Migration path as little and if I remember correctly there was a blogpost about having the option to package different multiple versions targeting old VS installations and also VS 2022 in a single extension, but since then I haven’t seen any update on that (maybe @madskristensen or @lyrichardson01 can help out with an update).

So much on the current state.

Since the discussion has become very heated and I really didn’t want to cause that much trouble I really want to say that all questions and input is valued, obviously also including questions for an ETA or a schedule.

I know that many people are using this extension as part of their daily routine so as with everything else I would also ask for an ETA for things I love and care about. There is absolutely nothing wrong with that as long as it is formulated with respect and in my opinion that definitely was the case.

So as the maintainer of this project I can just again try to assure you that every opinion and every post is valued because I do think that every comment / issue is a contribution to the project as well, because every issue that is being raised is also potentially affecting someone else. Contributions to Open Source is more than adding code IMHO.

Since I guess the most important part now is to get BuildVision working again with VS 2022, I’ll try to see what we are missing and probably compare with @chucker s branch, probably that can be reused to make it work.

If it still is not possible to having both supported things in a single version I’ll go ahead and create a new extension (e.g. BuildVision 2022), but for obvious reasons I would really love to prevent that from happening.

I can’t give you a timeline yet since I am still pretty busy with other things, but I can promise you that I’ll try to prioritize it a bit so that VS 2022 support is in soon.

So thanks again to everyone adding comments, asking for updates, or assistance. I really appreciate input of any sort and hope that we’ll continue this with respect and openess.

Thanks folks 😃

[StefanKert]

So here is a quick update.

It seems like one of the interfaces that is being used in BuildVision for listening to BuildEvents (icrosoft.VisualStudio.Shell.Interop.IVsSolutionBuildManager5) is conflicting somehow with version 17.2.

The interface type that is expected is located in Microsoft.VisualSTudio.Interop assembly, which is the case for most other BuildManagers, but not version 5.

I’ll do further checks and keep you posted 😃