I am using Visual Studio 2013 with Update 4. When I run performance profiling( from DEBUG> Performance and Diagnostics> Performance Wizard> CPU Sampling,
the profiler starts and stops without errors. But no reports are generated. When I tried to open the report from Performance Explorer an error message pops up showing:
"Invalid report: the data in the file is corrupt or has an unsupported format".
I tried searching for solutions, but I could only find solutions for VS2015 and 2017( I tried them by relating it to the functionalities in VS2013 but no result).
I am unsure but I think there is an incompatibility issue if you installed a newer version of Visual Studio on your computer.
Try to open the report generated (that fails to open in VS2013) in your newer Visual Studio. That did the trick for me with VS2017.
Tried profiling with Visual Studio 2017. It works fine.
Related
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 have the problem that Visual Studio 2013 crashes when I lock the computer or start another instance of Visual Studio.
I use Visual Studio 2013 with latest patches applied. I always start Visual Studio as Admin.
This seems to only happen with a certain big solution. This problem did not occur to me with other solutions.
I tried to delete the solution and make a clean checkout from TFS, but Visual Studio still crashes.
I know this is not much information, but do you have any idea how to fix this or how to what else I could check?
Additional Information: This still happens even with Visual Studio 2015 on a fresh Windows 8.1 installation...
Here's the error:
Use the following steps to solve the issue:
Source: http://resharper-support.jetbrains.com/entries/24765142-Visual-Studio-with-ReSharper-is-freezing-and-or-crashing
I would copy the solution with quotation but as you can see, there is a lot of text to edit.
Start Visual Studio using the /log switch. Then check the created log file for warnings and errors:
%APPDATA%\Microsoft\VisualStudio\11.0\ActivityLog.xml
If you use a Web Browser to view the file, it will be nicely formatted, due to the accompanying xsl-sheet.
Some time ago I started developing with Visual Studio 2013 Professional and everything worked well. But a few weeks ago I upgraded to the Ultimate version. But since then Visual Studio crashes when I load a project. VS just starts up normally, I can see the menu and log in and stuff like that. But when I open a project it crashes everytime. I tried to repair it VS in the control panel, but still the same problem... Then I reinstalled it but when loading a solution it crashed again. Now I downgraded to Professional again, but now even Professional crashes.
I have been searching on google for a long time to solve this problem. I tried to reconfigure the debugger, even reinstalled it, but no effect. A lot of forums say you have to delete the .suo file in the project, but even that doesn't work...
Is there a solution for this?
UPDATE
When Visual Studio crashes I get this error: https://i.imgur.com/VtaikJ5.png?1
My ActivityLog.xml is on OneDrive: https://onedrive.live.com/redir?resid=B3519F287A9CD3FC!2830&authkey=!AIUDHo1bCZan4Fk&ithint=file%2cxml
I already received the answer from the MSDN forum. And it was caused by the Web Essentials extension tool. And apparently with the Visual Studio Update 4 everything seems to be fixed. The extension tool was causing the error, and that error is fixed in the update.
Thanks for the support everyone!
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.
I'm getting the following error in Visual Studio 2008:
Unable to create the component used to
generate ASP.NET Intellisense
information. This can occur if Visual
Studio or the .NET Framework is not
installed correctly.
I've re-installed all versions of the .Net framework, run devenv /resetuserdata like suggested online, and did a repair install of Visual Studio. However, I still get the same error.
I can click past this message, but get subsequent errors about package loading errors. Then the project won't build when it build just fine days ago. Does anyone know how to correct this?
about 4-5 months before i was also getting this error, but i resolved that by unistalling each and every component of Visual studio and Sql server and then again installing it....
I still don't know y this error had come.