Specflow: Use AsyncPackage in VS Integration - yellow performance bars

[SabotageAndi]

We are currently using Package as base class in the Visual Studio Integration.

https://github.com/techtalk/SpecFlow.VisualStudio/blob/master/VsIntegration/SpecFlowPackage.cs#L40

To get rid of the yellow performance bars like this

we have to inherit from AsyncPackage.

[SabotageAndi]

More important because of https://blogs.msdn.microsoft.com/visualstudio/2018/05/16/improving-the-responsiveness-of-critical-scenarios-by-updating-auto-load-behavior-for-extensions/

In a later update, Visual Studio will completely disable auto-loading of synchronous extensions (update #2 mentioned above). End users will see a notification in Visual Studio informing them about extensions that were impacted.

[jkonecki]

I desperately need VS2019 support so I started playing with the upgrade.
As far as I can tell, support for AsyncPackage requires using Microsoft.VisualStudio.Shell.15.0, which in turn relies on Microsoft.VisualStudio.CoreUtility 15.6.27740, which in turn depends on .Net Framework 4.6.
My understanding is that the upgrade to 4.6 would be required, unless we could add support for VS2019 and keep syncronous Package.

[SabotageAndi]

@jkonecki The VS2017 extension is already build for .NET 4.6: https://github.com/techtalk/SpecFlow.VisualStudio/blob/master/VsIntegration/TechTalk.SpecFlow.VsIntegration.csproj#L52

Probably we should first switch to package references (https://blogs.msdn.microsoft.com/visualstudio/2018/10/10/simplify-extension-development-with-packagereference-and-the-vssdk-meta-package/).

BTW- disabling of loading of sync packages will be done in VS2019.1 (see update at https://blogs.msdn.microsoft.com/visualstudio/2018/05/16/improving-the-responsiveness-of-critical-scenarios-by-updating-auto-load-behavior-for-extensions/)

[SabotageAndi]

@jkonecki Why do you need already the support for VS2019? It's in it's first preview.

[jkonecki]

Purely because the preview is out and I would like to start using it :-)

On Thu, 3 Jan 2019, 13:33 Andreas Willich <[email protected] wrote:

@jkonecki https://github.com/jkonecki Why do you need already the
support for VS2019? It's in it's first preview.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/techtalk/SpecFlow/issues/1137#issuecomment-451143768,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABsWj0zhXiIDn84M4OqQoyFxxvDRHbi5ks5u_gajgaJpZM4TlZQk
.

[snow-jallen]

[ Sends happy thoughts to anyone working on this item so SpecFlow can support VS2019 ]

[SabotageAndi]

This issue is hopefully resolved with https://github.com/techtalk/SpecFlow.VisualStudio/pull/53.

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.