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!
Related
I have just installed Visual Studio 2015 Update 2 on my Windows 10 machine (both x64 versions) and I am having hard time getting the debugger to work. When I try to attach to any process via Debug menu, I keep on getting:
I have tried reinstalling, repairing Visual studio few times always get the same error. Even running a basic hello world console application gives the same error.
When trying to run a web application using the IIS Web Express 8/10.
Even though I am absolutely sure that the message of corrupt installation is misleading, but I even have tried repairing visual studio from control panel and nothing seems to work. I dont even get any error logged anywhere which is keeping me stumped for last 1 day. This is what my VS installation looks like:
I am running the visual studio as administrator. I am pretty sure this is not a windows error as I tried installing VS2012 and debugging works in it.
Any ideas?
Recently started using Visual Studio 2012, converting SSIS packages from 2008, and seem to be unable to set breakpoints in Script Tasks. The error we're receiving says
Cannot start debugging. Pre-debugging negotiations with Host failed.
Cannot seem to find any information about this error, or what's causing it. There is also a brief flash of a dialog box that says
Visual Studio has encountered an unexpected error
but that disappears quickly.
This issue has been resolved. The input parameters were set incorrect and hence was failing. It has been fixed now
I think you install new version of Visual Studio you just have to uninstall the Visual Studio tools for Application for the new version then repair the Visual Studio tool for Application 2012 and every thinks will be good
I can't debug my Sharepoint 2010 project. Visual Studio 2010 shows me the following error message:
Unable to attach to he process. An error occurred that usually indicates a corrupt installation (code 0x80040154). If the problem persists, repair your Visual Studio installation via 'Add or Remove Programs' in Control Panel.
I experienced this problem some days ago for the first time.
At first repairing helped, but after a little time the error occurred again.
I have tried restarting computer, too, after which the problem was gone for only a little time.
I have uninstalled/reinstalled visual studio, but still no success.
How can I solve this problem, I have no idea about the reason.
EDIT: I have noticed that the problem occurs only when I try to debug a workflow code.
I have had this issue in the past and solved it by ensuring I'm compiling the code to x64. Check your settings in Visual Studio. SharePoint is 64bit only.
Good Luck.
I had a problem with the javascript debugger on a web project, and I got a similar error message. The fix was: Closed all instances of Visual Studio. I threw away the app in inetmgr, and re-opened visual studio with my solution that has my web app. It re-created the virtual directory on opening. Javascript debugger started working again.
I recently installed Update 1 for Visual Studio 2013. Every time my program throws an exception, the Visual Studio debugger crashes - whether or not the exception is handled.
Visual Studio also crashes whenever it hits a breakpoint.
The Windows Error Reporting dialog pops up and gives the options to debug or restart Visual Studio. If I click debug and and open with VS, it also crashes - debugging itself! This is leading me to believe that there is not a problem with my app, but rather with Visual Studio.
Visual Studio Professional 2013 (12.0.30110.00 Update 1)
Windows Server 2012 R2 x64
Any ideas?
The problem, it turns out, was that I had installed a trial version of Redgate Tools' .NET Reflector. The trial's expiration had coincided with my installation of Update 1. .NET Reflector was throwing a NullReferenceException and hence crashing Visual Studio.
The solution was simple: disable or uninstall the .NET Reflector extension.
My proposal is: get more data about the crash and see whether it's caused by Visual Studio itself or any plugins which might not be compatible any more.
Set up the registry for Windows Error Reporting to store local dump files, reproduce the crash and analyze the dump in WinDbg (because Visual Studio is not working well).
Some steps in WinDbg:
open crash dump
.symfix c:\mysymbols
.reload
.exr -1
.loadby sos clr (if it's a .NET exception)
!pe (if it's a .NET exception)
!clrstack (if it's a .NET exception)
I also get Problems with IDE crashing after installed "update 1". My Workaround: uninstall that update. It is really Buggy and NOT production ready. Maybe it is caused by a Extension, but I dont have time to debug Tools I have to use to get my work done, I Need working Tools.
I've been stuck in this problem for 3 days until I discovered that the problem was in try-catch blocks. Viewing this article: http://msdn.microsoft.com/en-us/library/vstudio/0yd65esw%28v=vs.110%29.aspx, I realized the importance of not leaving a "catch" empty.
Well, this problem happened to me while developing a simple sequential workflow SharePoint 2013 in Visual Studio 2013 in "OnTaskChanged" methods.
I hope the answer may help someone else.
Mostly it happens if we open a team project from tfs 2008 or tfs 2010, but crashes can happen any time.
When VS is closing down, it crashes nearly every time.
Tried trial RTM and our MSDN download - same story. Tried on three different PCs - same issue. Tried on 32 and 64-bit Windows 7 and Windows Server 2008 R2 - crashes.
Is it just our luck or does it happen to you to?
Here are some tips that will hopefully help you identify the problem:
http://blogs.msdn.com/kirillosenkov/archive/2010/02/08/how-to-investigate-and-report-visual-studio-issues.aspx
Ideally, get a call stack of the devenv.exe main thread with symbols loaded, and post it here (or even better), attach to the Connect bug. From the stack we'll likely be able to tell what kind of problem it is.
I logged it as an issue on Microsoft Connect.
There is a new release of the TFS Power Tools and Visual Studio 2010 Productivity Power Tools which seem to reduce the instances of VS crashing (although it still seems to crash from time to time). It might be worth checking out if you use either add-in.
Apparently, the crash was caused by using a DNS name in Connect to Team Foundation Server.
I replaced that with the IP address of the TFS server and the crashes went away.
We have two Windows Server 2003 DNS servers, and it looks like Visual Studio 2010 does not communicate with them correctly. Visual Studio 2008 connects to the TFS without any issues.
Apparently, there a bug:
"Large Visual Basic project crashes when closed"
http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=29797