Errors in Visual Studio Behaviour, that can hardly be explained
Misconfiguration of local Visual Studio configuration through roaming profiles or one-time events
At first-time start of Microsoft Visual Studio ist starts it's own configuration of the user in the corresponding local userprofile under %appdata%MicrosoftVisual Studio<version> and the Current User Settings in the registry.
If this configuration seems to be corrupt (f. ex. through a configuration mix by using different Visual Studio machines and active roaming profiles), it can simply be corrected by a new config process through
in a command shell (cmd.exe) or the "run..." entry in start menu.
Disclaimer:The information provided in this document is intended for your information only. Lubby makes no claims to the validity of this information. Use of this information is at own risk!
About the Author
Author: Wim Peeters - Keskon GmbH & Co. KG
Wim Peeters is electronics engineer with an additional master in IT and over 30 years of experience, including time spent in support, development, consulting, training and database administration. Wim has worked with SQL Server since version 6.5. He has developed in C/C++, Java and C# on Windows and Linux. He writes knowledge base articles to solve IT problems and publishes them on the Lubby Knowledge Platform.