Fails to launch on 2022 17.2.0 Preview 5.0

[chucker]

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?

[michael-hawker]

I'm seeing the same (with the same error message) in the latest 17.2.0 stable release.

<entry>
    <record>959</record>
    <time>2022/05/10 22:33:51.518</time>
    <type>Error</type>
    <source>VisualStudio</source>
    <description>SetSite failed for package [BuildVisionPackage]Source: &apos;Microsoft.VisualStudio.Validation&apos; Description: Cannot find an instance of the Microsoft.VisualStudio.Shell.Interop.IVsSolutionBuildManager5 service.&#x000D;&#x000A;</description>
    <guid>{837C3C3B-8382-4839-9C9A-807B758A929F}</guid>
    <hr>80131500</hr>
    <errorinfo></errorinfo>
  </entry>

[StefanKert]

Hi folks,

currently checking this and I'll let you know if there is a fix available :) thanks for reporting

[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 :)

[GitSparTV]

+1 for this

[PeterJarrettUK]

Annoyingly I've just had the 17.2 update drop onto my pc as it's now full release and comes down via VS Auto Update - and now I've got the same BuildVision fail to load - thanks to you writing such a great extension I'm really missing it now VS has killed it - can't wait for a fix :-) !

But thank you again for a great add in - keep up the great work!

[latenightsurfer]

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 :)

can you estimate when there will be a fix available?

[jzabroski]

can you estimate when there will be a fix available?

@latenightsurfer Can you go fix the issue? These questions aren't helpful and what makes open source software in .NET so bad at times.

[Janek91]

@latenightsurfer any news?

[mitchcapper]

@latenightsurfer any news?

Seriously take a hint. Unless you have something to contribute in terms of technical assistance, technical details, or monetary assistance for the project please do not post unhelpful comments. These sort of comments can be demotivating. One of the contributors has already said they will post when they have updates. SO you want 'news' @Janek91, hit the subscribe button in the upper right of the issue report, you will get notified when there is a meaningful update (or someone else makes a useless comment).

[kenny1983]

@latenightsurfer any news?

Seriously take a hint. Unless you have something to contribute in terms of technical assistance, technical details, or monetary assistance for the project please do not post unhelpful comments. These sort of comments can be demotivating. One of the contributors has already said they will post when they have updates. SO you want 'news' @Janek91, hit the subscribe button in the upper right of the issue report, you will get notified when there is a meaningful update (or someone else makes a useless comment).

Wow...I totally get where you're coming from mate, but geez, that was just a bit harsh don't you think??

[chucker]

@kenny1983 Mitch isn’t the developer, FWIW

[kenny1983]

Yeah I realise that now. Edited my comment accordingly.

…

On Fri, 16 Sept 2022, 9:19 pm Sören Nils Kuklau, ***@***.***> wrote: @kenny1983 <https://github.com/kenny1983> Mitch isn’t the developer, FWIW — Reply to this email directly, view it on GitHub <#120 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACHCHCQZ5MKZ3T2DILBKTQTV6RJSJANCNFSM5UWGXLBQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[mitchcapper]

Wow...I totally get where you're coming from mate, but geez, that was just a bit harsh don't you think??

Yes. As subtly generally doesn't seem to work. The developer previously stated

• I'll do further checks and keep you posted :)

• @latenightsurfer then felt asking the developer if they could estimate when it would be fixed was appropriate

• jzabroski then pointed out the fact its open source so if you need it fixed you are welcome to contribute to do so and the fact these questions annoy many developers.

• Then @Janek91 commented another useless comment of essentially whats going on with the fix?

These things to me show either @Janek91 did not read or think through the comments thus far to realize how that is likely to be annoying, or they did and decided hey who cares im going to ask for an update anyway. This is also reinforced as they directed the update request to a user who isn't a contributor on this project. Further, if the dev didn't respond to @latenightsurfer why should you expect them now to answer you?

As clearly jazbroski's comment was either not understood nor not headed it seemed something more blunt was in order. Janek is not new to GH and likely aware how these thing work as well.

All of this is not a new phenomenon to say the least, it happens on most projects and annoys most developers and even when someone has already pointed that out in this very bug report it is ignored and the me first give me an update approach is still taken.

@kenny1983 comes along and mistakenly assuming I was the developer stated:

If you're going to be like that, I'll completely forget about ever supporting this extension. Thanks 👍

or essentially said: Boy how rude you are, I will never even think about supporting this extension in the future. Now I am not sure if that means @kenny1983 has provided support for it in the past, or was about to make some contribution, (or more than likely neither) but lets think about that statement. They were mad as they thought the developer was being rude, however jzabroski tried to point it out in a nicer fashion, no luck. As not the project owner I can make my comment and hopefully these sorts of users will finally get why these actions are potentially so annoying for so many without a lot of backlash on the actual owner.