Visual studio 2010 crashes every now and then while developing for windows phone 7. Most of the times the enviornment hangs for a few seconds shows a message that display driver recovered from some critical error.Some time its a BSOD. I am experiancing the same in 2-3 machines. Is it just me or something else is wrong?
Related
When running my UWP Xbox one app with the debugger attached, if I try to take a snapshot it begins counting memory objects and then the app closes and the debugger disconnects. I tried using Visual Studio 2017, as well as Visual Studio 2019 and I also tried repairing my Visual Studio installations. Both versions exhibit the same behavior.
So I have a machine which runs Windows 10 with Visual Studio Ultimate 2013.
But everytime I start the program it crashes within 1 minute, even without even moving my mouse.
When it crashes it gives me the following error: An unhandled Microsoft .NET Framework exception occurred in devenv.exe [6820]
I have noticed that the error started coming up after I connected to a Team Foundation Server, but I dont know if it has anything to do with the issue.
Furthermore, I am running a clean Windows install so that shouldn't be the problem either.
At this point I really don't know what to do, and I have my exams in two weeks, with which I need Visual Studio with Team Foundation Server.
Please help me with this, it would be very much appreciated!
I installed 2 versions of the free trial for Visual Studio 2013, first Professional, then Ultimate. When I try to launch the first time, it locks up and eventually gives a "not responding" message. The first time I try, it crashes the operating system with a "kernel_inpage_data_error". I'm running Windows 8.1.
I've tried multiple times to repair the install, and tried a total uninstall/reinstall. I get the same result every time.
Can any Windows Phone Application developer help?
When i run my project, emulator starts and shut down, and the error The interface is unknown is displayed in error log in Visual Studio.
It was running fine the other day.
What should i do to get rid of this error?
If you are using Visual Studio 2010, the window phone emulator for widow phone 7 series suites your PC. if you are experiencing problems with it, simply download Visual studio 2010 service pack 1 and re-install the tools. you can also update your .net frameworks from windows update.
if you are using Visual studio 2012, then you must be using the window phone 8 emulator which runs on only 64 bit and window 8 pro (or advanced) machines. it works on the visual machine. so you can re-install your Hyper V drivers or re-install the SDK
i hope this help fix the problem permanently.
Identified what the problem was :-)
"Windows Phone Emulator-512" is compatible with only Visual Studio 2012; it is not backward compatible with earlier versions of Visual Studio. So, now i used "Windows Phone Emulator-256", it's working fine :-)
Thanks to: https://msdn.microsoft.com/library/windows/apps/ff402563(v=vs.105).aspx
I just added a third monitor to my system (NEC E222W) which my NVidia GeForce 9500 GT card is able to rotate such that I get 1050x1680 resolution. However, when using this mode Visual Studio 2010 SP1 (10.0.40219.1 SP1Rel) consistently locks up (grabbing 50% of the CPU) until I kill it whenever I interact with TFS. I can work in VS 2010 until I try to do anything with TFS.
I can open up Visual Studio without issues on my other two monitors and check stuff out, etc., but the minute I move the application to my 1050x1680 monitor and start the TFS dialog, the application hangs.
Anyone have this issue? I'm pretty current on the NVidia driver (191.07) and Windows XP SP 3 is current with Microsoft Update. I'm running under a non-administrator account.
Internet has not been helpful. The only thing I found was this:
http://social.msdn.microsoft.com/Forums/en/vseditor/thread/ce9134aa-b444-49e8-99f2-01b67404156a
This: Visual Studio 2010 Freezes when using TFS is unrelated.
I am able to fire up VS 2010 on the 1050x1680 monitor, work, then shift the existing instance over to another monitor to interface with TFS (check in/out) and then shift the application back to the 1050x1680 monitor successfully. I strongly suspect something is broken with the TFS checkout dialog window.