I have been working on a particular solution for a few months now without any problems. The last thing of significance that I remember doing was refactoring the name of a custom control inheriting from RichTextBox. I don't know if that is related to the problem but it seemed to be when the problems started occurring. For some reason now when I show the main form in design view and save any changes I get the message "Visual Studio has stopped working blah blah" and it restarts.
I seem to be able to load and make changes to other solutions ok.
So far I've tried:
Deleting .sln and v12.sln files
Have tried uninstalling NuGet. (I don't have any extensions other than NuGet and Visual Studio Extensions for Windows Library for JavaScript)
I don't have resharper
I have tried to start in /SafeMode but I keep getting the error "'Visual Studio Component Model Host Package' package did not load correctly". I can't seem to load any solutions in SafeMode.
Repaired VS2013 installation twice
Restarted my computer many times
Tried writing a log file using /log switch but can't really understand how to interpret it.
Any pointers would be very welcome.
I'm currently developing a windows modern app using Foundation for Apps and cordova. The app crashes in many ways during navigation, sometimes even immediately after running it.
The crash is this one
And i can't manage to debug it in any way.
I've tried setting up a window.onerror and a WinJS.Application.onerror catch all function with no results. Apparently the crash happens at a lower level. I've also inspected the event viewer but no info are available.
What happens is apparently similar to this question: How to debug unhandled win32 exception in WinJS Win8 store app which is unfortunately unsolved.
What are my options here?
I had the same issue with Visual Studio 2015, Windows 10 and cordova 5.1.1 when I transfer the project to another dev environment. It only occurs at the Windows-x64 app build configuration for the local machine.
After successful building, the app window launches shortly and after that, the win32 exception like the screenshot from sPoz came up. It was reproducible every time.
I try to repair Visual Studio and also I checked the environment variable from my solution as it is described in this Microsoft Article. But I had no luck.
Nothing helped, but simply open the config.xml file and change the Windows Target Version from "Windows 10" to "Windows 8.1" solved the problem and I could run the app with no error:
After that I can turn back to "Windows 10" and everything is fine. This was reproducable on two dev machines.
I do not exactly know if the moved project was the source of the problem and maybe the rewritten config.xml triggers any rebuild mechanism.
Most likely you are hitting an issue related to DOM Ex WWAHost.exe error on Windows 8.1 (apparently fixed on Win10). There is a workaround that should work for most apps; before you click around and get the WWAHost.exe exception, close the DOM Explorer window. This should enable you to debug by hitting breakpoints, etc. If you need to use DOM Ex against a Windows target, you might need try debugging against a remote device (see Kenneth's suggestion here: Why is Cordova Windows 8 app causing an unhandled win32 exception occurred in wwahost.exe?)
What are you using to develop the app ? The Visual Studio Tools for Apache Cordova ? Or Cordova with CLI ?
If you are using the plugin, you must launch the generated WP project to debug. The debug of WP app is not supported currently with the plugin.
I was getting same error during development of cordova windows tablet application, using Visual Studio Enterprise 2015. So far, I was doing try to close DOM-Explorer and use breakpoints and javascript console. After that, while searching javascript intellisense issues with Visual Studio, I figured out that my problem was fixed. What I did to get rid of this problem is that:
Open Tools > Options
Select Text Editor > Javascript > Intellisense > References
Add following references ( angular.intellisense.js, domWeb.js, domWindows_8.1.js ).
I don't know what are the correct reference files, but with these 3 reference files added, my problem has been solved.
So I just updated to IE10. When I try to debug my web app's javascript, my breakpoints are all just outlines with a little triangle and say in the tooltip:
The breakpoint will not currently be hit. No symbols have been loaded
for this document.
IE10 is started when I start debugging and it goes to the website like IE9 always did. If, in VS 2010, I go to Debug > Attach to Process... and select the iexplore.exe process, as my javascript executes it will hit and stop at breakpoints like it always would with IE9 and everything is peachy until I kill IE10 and start debugging again.
I've made sure that Javascript Debugging is enabled in IE10 and any "solutions" I find online all say to uninstall/reinstall VS2010/IE10 and see if that helps. I already know that VS2010 is capable of debugging, it's just not attaching the debugger properly. How can I fix this so that debugger attaches properly and will hit breakpoints and exhibit the usual behaviour?
Another StackOverflow Post recommends installing VS2012 (any version) and that should fix your issue when debugging JavaScript in IE10 with VS2010.
This may fix JavaScript debugging issue in IE10:
Close Internet Explorer
Press start and type CMD
Run one of these commands in command prompt
32-bit OS
regsvr32.exe "%ProgramFiles(x86)%\Common Files\Microsoft Shared\VS7Debug\msdbg2.dll"
64-bit OS
regsvr32.exe "%ProgramFiles%\Common Files\Microsoft Shared\VS7Debug\msdbg2.dll"
There is another thread on this issue, as Elijah mentions, and this answer is probably more appropriate there, but that thread is closed to me because I'm a new poster. Corey has already mentioned that he can't install VS2012 at this time, but it may be useful to others.
I experienced this same problem after updating to IE10. I already had VS2010 and VS2012 with Update 1 installed, and none of the recommended fixes (including the msdbg2.dll registration) worked for me. What fixed my problem was to reapply Update 1 for VS2012, choosing the "Repair" option. I can now debug javascript in VS2010 again.
Configuration:
Windows 7, 64 bit
Microsoft Visual Studio Professional 2012 RC Version 11.0.50522.1
RCREL
Running VS in administrator mode
The VS solution contains a web
application, with target: .NET Framework 4.
When I press F5, the solution builds... and nothing else happens.
Happens with both IIS or the VS Dev Server.
Happens with Platform Target of "Any CPU" or "x86"
If instead, I use the Debug / Attach to Process... menu, after a few seconds, I get:
"Debugger is Busy" - Debugger is performing a remote operation that is taking longer than expected. This dialog stay until I click "Terminate" and confirm it.
Then this dialog appears:
"Microsoft Visual Studio"
"Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named [COMPUTER NAME]. The network connection to the Visual Studio Remote Debugger has been closed."
After clicking OK, the 'normal' "Attach to Process" window finally shows up. In it, the list of "Available Processes" is empty.
Any suggestions or clues?
The main points that I wonder about:
Why is the list of processes empty? It is not surprising that the debugger does not work if it cannot see any processes.
Why is it trying to do "remote" debugging, when it is just accessing the local computer?
(Cross posted on social.msdn)
I had the same problem in VS 2012 (not the RC, but the final release) using a VS 2010 project. It would build fine, but the debugger would not start. So, I modified the solution file:
Changed "Format Verion 11.00" to "Format Verion 12.00"
And changed "# Visual Studio 2010" to "# Visual Studio 2012"
It's a workaround for now until my company upgrades its projects to VS 2012.
I've got a similar setup and I'd followed all the suggestions here and on Microsoft Connect - none of which worked for me. The only thing that did work was renaming MSVSMON.EXE in the x64 folder to MSVSMON.EXE.OLD and copying in the file from the x86 folder in it's place. I'm not sure if there are any other implications in doing this but it seems to have solved the problem in my case.
I eventually resolved this problem by deleting the msvsmon*.* entries in the \Windows\Prefetch folder. After doing so I could debug normally.
Ultimately, a Repair of the VS2012 resolved this issue for me. I followed the advice found at your social.msdn cross-post without any resolution (Devenv.exe /SafeMode /ResetSettings /ResetSkipPkgs and /Setup). Like you, my solution (VS 2010 SP1) also has a web application (targeting .NET 3.5), and the startup project is set to a winforms app. The ASP.NET development server did not start, nor did the app I was trying to debug.
Note that this issue was also posted to Connect at this link (by you?). If anyone else sees this issue, the Connect folks are requesting running the Microsoft Visual Studio 2012 Feedback Tool to collect data. As I started the Repair process prior to finding the Connect issue, I did not and was not able to provide feedback to MS with logging.
Seen a similar issue when running both Visual Studio 2010 and Visual Studio 2012 at the same time. Closing Visual Studio 2010 allow the debugger to start working in Visual Studio 2012.
I had the same issue - starting debugger just told me what a good job it had made of the build and the decided that that was enough.
I feared the worst, but luckily for me a reboot fixed the problem.
I know that this is therefore a pretty useless post in as far as offering help to anyone suffering with this issue, but I thought it was worth noting the point as it shows a) another person with the same problem so please fix it MS, and b) that sometimes a reboot fixes it so maybe that tells the maintainers something.
If you are opening a VS 2010 project with the new VS 2012 version it's probably your bin and obj folders that are causing the problem,deleting them solved the problem for me.Or you could clean your solution but I preferred manual deletion.
I just closed and reopened VS. This seemed to fix my problem
On another computer, with the RTM of Visual Studio 2012, I opened an older project and found that I could not press F5 to start the application. All that seemed to happen was a message in the status bar on the bottom edge of the window: "This item does not support previewing".
This solution had two projects, and the correct one was bold in the Solution Explorer, presumably indicating that it was the startup project.
However, after selecting the project and choosing "Set as Startup Project" in the context menu, I was then able to use F5 to run and debug it.
It turns out that the "This item does not support previewing" was nothing to do with the problem, but is a message that shows on the status bar whenever the item just selected in the Solution Explorer does does not support previewing.
For what it's worth, I found that I received this error message when I had an entry missing in my hosts file. I am using local domain aliases and the one I was trying to debug with wasn't in hosts. Adding the missing entry solved the problem for me.
Just copy all dte*.olb files, from C:\Program Files (X86)\Common
Files\Microsoft Shared\MSEnv to C:\Program Files X86\Microsoft Visual
Studio 9.0\Common7\IDE.
From https://mycodepad.wordpress.com/2013/12/07/visual-studio-2012-4-run-as-administrator-the-application-cannot-start-error/
Just my two cents,
I have experienced this issue twice now and it turns out after all of the suggestions I tried, it was BitDefender on my local machine that was doing this. So my fix for this problem is to try adding in exceptions to the local security software into the firewall and AV parts of it. Tell it to ignore the msvsmon.exe and devenv.exe altogether and see what difference that makes.
Otherwise try ripping it off altogether and see if the it lets you debug your solution.
You can see here for more info: http://forum.bitdefender.com/index.php?showtopic=37028
I installed the latest BitDefender version and all was fine for me.
I personally encountered some comparable problem: Visual Studio 2010 did not begin debugging but froze.
When I clicked VS it displayed a "Wait some more" or "Switch to" message box which didn't help me.
Using a task manager I could kill the *.vshost.exe process which brought VS back to life but aborted the debugging. Launching the program without debugging started the application instantly.
Solution:
Disable the indexing service for your code directories! Either deactivate the index service or uncheck the folders in the Indexing Service control panel.
Had this problem for a C++ application. Looking at the devenv.exe events in ProcMon pointed me to it trying to load a Visual Assist configuration file, which I had in my disk cleanup zeal accidentally deleted. Removing and then installing the extension again fixed it for me.
I have fixed the same issue by checking off the "Enable the Visual Studio hosting process" option from the start-up project Properties->Debug - Enable Debuggers options
All you have to do to fix this is go "Project > Set as StartUp Project" then hit F5 or the debug button and it will work!!!
We use NugetPowerTools PackageRestore to avoid putting our packages folder in svn. This works building .NET projects with Visual Studio and MSBuild. It also works building Silverlight projects with Visual Studio.
However, when we use MSBuild to build Silverlight projects, the build fails. This appears to have to do with the tasks in Microsoft.Silverlight.Common.targets. Looking at the MSBuild output, it appears to get to the step GetXapOutputFile before it errors. Something either in that step, or after that step, is looking for the packages, but the package restore does not run until after all of this. Building a second time will succeed.
What is different from pressing build in Visual Studio than running MSBuild? Is there a command line switch I am missing?
If that won't work, is there some way I can change the NuGet.targets created by NuGetPowerTools or something I can put in my csproj file that will switch the order these steps are run?
I am running MSBuild Solution.sln /target:Clean;Rebuild
Edit
I've update NuGet to v1.6, removed all traces of NuGetPowerTools and I am now using the built in Package Restore option. I am still getting this error.
Edit Again
A discussion around this issue has come up again. I've tested this now with NuGet v2.0 and it is still happening.
This has been corrected in NuGet v2.1.31002.9028. The details can be found in this commit.
For existing solutions, you will need to delete ./nuget/NuGet.targets from your solution. Do this through Windows Explorer. Deleting it through Visual Studio will only remove the file from your solution, it will leave the file alone.
Once you have done this, right click on your solution and select "Enable Package Restore". This will recreate NuGet.targets with the fix.