-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Visual Studio crashes when I click on Team Explorer #923
Comments
Here's some more debug output:
|
I hardened the
|
It looks like something added the following to one of my projects.
Apparently this means copy these files into a temp directory and stuff them into the |
It appears I may have dumb thumbed adding a reference and added an analyzer instead. When I removed the Unfortunately this issue returned, with Visual Studio loading assemblies from this location instead:
It looks like there can be a fight between different assembly resolvers, with whichever resolver gets added first deciding where assemblies get loaded from. 😭 Luckily the assembly resolver that appears to come with Visual Studio is only likely to resolve one of our assemblies, if it's referenced by a project. This is only likely to happen in one of our projects or in a project that is attempting to extend GitHub for Visual Studio. There are a few mitigations for this:
SummaryThe root cause of this issue is one of our assemblies getting loaded into the wrong codebase. |
Added a workaround related to #923 that gives our resolver a chance to run first. Be more specific about which assemblies might be resolved (include PublicKeyToken). They must start with "Microsoft.TeamFoundation." and end with ", PublicKeyToken=b03f5f7f11d50a3a".
This was particularly an issue when the It should no longer be a problem now that #914 has been merged. |
Added a workaround related to #923 that gives our resolver a chance to run first. Be more specific about which assemblies might be resolved (include PublicKeyToken). They must start with "Microsoft.TeamFoundation." and end with ", PublicKeyToken=b03f5f7f11d50a3a".
The following was sent to debug output:
The text was updated successfully, but these errors were encountered: