-
Notifications
You must be signed in to change notification settings - Fork 51
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
Unresponsive during VS startup #172
Comments
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 |
16 s is still a lot if it is correct. |
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 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) |
Description
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
The text was updated successfully, but these errors were encountered: