Remove GetService(...) calls from VS MEF importing constructors #10168
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We observed a hang during solution load because
VisualStudioEditorDocumentManager
retrieves theIVsRunningDocumentTable
service in its constructor. When this constructor is called on a background thread, it results in an implicit marshal to the UI thread in order to retrieve the service and QI for its COM interface. This change fixes that issue delaying the request forIVsRunningDocumentTable
until it is needed and running on the UI thread.In addition,
VisualStudioFileChangeTrackerFactory
had a similar issue but withIVsAsyncFileChangeEx
. BecauseIFileChangeTrackerFactory
is imported byVisualStudioEditorDocumentManager
, I've fixed this service as well.