-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Wait until solution load before we kick off all our nuget work. #9663
Wait until solution load before we kick off all our nuget work. #9663
Conversation
c536146
to
24a0874
Compare
Tagging @dotnet/roslyn-ide @jasonmalinowski @heejaechang |
retest vsi please |
@@ -161,6 +166,14 @@ private void LoadComponents() | |||
|
|||
LoadAnalyzerNodeComponents(); | |||
|
|||
// Ensure the nuget package services are initialized after we've loaded |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
new MEF import will be also perf impacting thing for solution open.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah, sorry, git collapsed region and it looked like code belong to initialize.
if possible, importing and running from background thread will be even better.
👍 |
// Start the whole process once we're connected | ||
_installerService.PackageSourcesChanged += OnPackageSourcesChanged; | ||
OnPackageSourcesChanged(this, EventArgs.Empty); | ||
_started = true; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this happen before the call to OnPackageSourcesChanged
in case anything in that method looks at it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
actually, i just realized this isn't even necessary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope. Scratch that. Still necessary.
This boolean is just so we know if we've actually done the event hookup. That way we know if we should disconnect on 'Stop' down below. Where it comes here shouldn't really matter.
👍 |
Any reason not to get conflicts dealt with and merge this? |
Yup. I'll take care of this PR. |
test vsi please |
No description provided.