Skip to content
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

Fix MEF composition error #2386

Merged
merged 1 commit into from
Oct 16, 2018
Merged

Fix MEF composition error #2386

merged 1 commit into from
Oct 16, 2018

Conversation

jaredpar
Copy link
Collaborator

This fixes a MEF composition error that occurs more frequently on older
versions of Visual Studio. There appears to be a timing issue with
accessing the output window on the UI thread during composition.

Unfortunately I'm not able to see what is going wrong as it's happening
within the DTE layer. The fix though is pretty straight forward:

  1. Delay the initialization of the Output Window to idle
  2. Catch exceptions coming from that code and raise errors vs. letting
    them be unhandled

closes #2249

This fixes a MEF composition error that occurs more frequently on older
versions of Visual Studio. There appears to be a timing issue with
accessing the output window on the UI thread during composition.

Unfortunately I'm not able to see what is going wrong as it's happening
within the DTE layer. The fix though is pretty straight forward:

1. Delay the initialization of the Output Window to idle
1. Catch exceptions coming from that code and raise errors vs. letting
them be unhandled

closes #2249
@ricksladkey
Copy link
Collaborator

It sounds like you were able to repro the issue. That's great!

@jaredpar
Copy link
Collaborator Author

Yeah finally reproduced this. I'm still not entirely sure what is needed to make it happen. I have a number of machines with VS2107 and VS2015 installed but only one reproduced this issue. Think it may have something to do with the solution state loading. Essentially whether or not the output window was visible when you last closed the solution or something along those lines. Either way though fix is basically the same.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants