This is an old thread but the same symptom has come back but based on a new cause.
Please, clear the Visual Studio component cache, restart Visual Studio and retry. I suspect that you have some version conflict between components after update. The component cache is located at
Please, clear the Visual Studio component cache, restart Visual Studio and retry. I suspect that you have some version conflict between components after update. The component cache is located at
Users\{yourusername}\AppData\Local\Microsoft\VisualStudio\14.0\ComponentModelCache
and afterwards restart the Visual studio.
No comments:
Post a Comment
Note: only a member of this blog may post a comment.