Paket.VisualStudio icon indicating copy to clipboard operation
Paket.VisualStudio copied to clipboard

Unresponsive during VS startup

Open rojepp opened this issue 7 years ago • 3 comments

Description

capture

VS gives a message on startup about Paket being unresponsive for 16 sec during startup

Repro steps

Start Visual Studio with Paket for VS installed

Related information

  • Win 10
  • VS 15.17.4

rojepp avatar Jul 06 '18 08:07 rojepp

The issue is that with VS 2017, now all extension who doesnt do async loading, are flagged as not responsive (that warning).

Also R# and VF# was flagged 😄 like i'd ever want to use F# without VF# or C# without R# 😆

Anyway, guide to conversion and more info is in https://docs.microsoft.com/en-us/visualstudio/extensibility/how-to-use-asyncpackage-to-load-vspackages-in-the-background#convert-an-existing-vspackage-to-asyncpackage

enricosada avatar Aug 01 '18 08:08 enricosada

16 s is still a lot if it is correct.

JohanLarsson avatar Aug 01 '18 09:08 JohanLarsson

That's pretty much the time used by all extensions to start up, 8+ seconds. And whole extension, so some parts are reused by others extensions because shared that message is only for the time the extension need to initialize.

But yes, fixing that will improve a bit the freeze/wait at VS startup but not while 14 sec in my experience with similar changes in other extensions (like github, r# etc), because while you can do some part in background others will need ui thread anyway by design (that's how VS extension acquire a lock for an action pratically)

enricosada avatar Aug 01 '18 09:08 enricosada