![]() ![]() ![]() For Visual Basic Express type, “ vbexpress /resetuserdata”.Depending on the SKU installed, type the following:.If you’re using an Express SKU your steps will be a bit different: If you wish to reimport your old settings, go to Tools->Import and Export Settings, select “Import selected environment settings and browse to the.Start Menu->Run (or Windows Key + R for the keyboard savvy).If you have customizations that you want to save, please copy CurrentSettings.vssettings under “ %USERPROFILE%DocumentsVisual Studio 2010Settings” to another location. NOTE: The IDE will be reset to its default state and all customizations will be lost. To workaround these issues, you’ll need to reset your settings file. If you have floating tool windows (e.g., drag off Solution Explorer to another monitor or show the Find dialog), minimize Visual Studio, and then close Visual Studio from the minimized state, on the next launch you will hit this error. The second way to get in this state is by a corrupted window profile – the file that persists your IDE window state.This was already covered by Brittany in her excellent blog post. The first issue is importing a non-TrueType font from a previous version of Visual Studio.Both of these issues have been fixed for RTM, and, fortunately, there are workarounds for Beta 2. In Visual Studio 2010 Beta 2, there are two straightforward ways to get into this state. Now that I’ve given you the background, what do you do if you hit this? We’ll start with the most common case, at least for Visual Studio 2010 Beta 2. There are a few alternative approaches that we are investigating for RTM around providing a more meaningful error message. Because of the managed to native interop on the initialization thread, all the code gets back is an HRESULT it loses its error context. Now, you may be asking, “Well the least you could do is give me some exception message that would make debugging this easier, right?” Unfortunately, no. If any one of these operations encounters a critical exception from which it cannot recover (which means VS won’t be able to initialize properly), an error is raised and the user is presented with “The application cannot start.” When Visual Studio is launched, the initialization code branches off and begins to perform a number of tasks such as reading the window layout, importing the saved settings, loading a number of. There are a number of scenarios that will cause the IDE to get into this state, which makes diagnosing this issue rather non-trivial. ![]() I wish I had a quick, easy, one-line answer for why this happens, but as with most things in life, it isn’t that simple. “Well, it was working fine this morning!” you say. So, you’re sitting on your couch and all of sudden…epiphany! You’ve got the solution to the code problem you’ve been working on for a few days! You go to fire up Visual Studio, and instead of being treated with a new instance of VS you are presented with this - the dreaded error: “The application cannot start.”: Outside of work, I’m an avid football fan, love winter sports, and always enjoy some quality mac and cheese. Prior to my current duties, I was the SKU manager for the Visual Studio Express products. No, not the “ Isolated” or “ Integrated” Shell, but the core VS IDE – it’s UI and services. Short Bio: I started at Microsoft as an intern in 2005 and have been working in Visual Studio ever since. Weston Hutchins – Program Manager, Visual Studio Shell Team ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |