**Update : apparently it's because my solution is too large ( the projects and assets it self ~56 GB). So after I switched to SSD Drive the crashes rarely happens. Well, perhaps the root problem was not this because it still crashed :) .
I am using MS Visual Studio Express 2013 for Windows 8.1.
I have a problem when trying to Find (Ctrl+F) and Look In Entire Solution, visual studio always crashed.
Anyone know what should I do?
Or maybe the workaround for this problem. :)
Try cleaning the solution, it worked for me.
From the menu bar: Build > Clean Solution
Switched the drive to SSD Drive will help, the crashes still happen but the rate is low.
Related
I had this working OpenCV project in visual studio 2017. I update Visual Studio to version 15.6.4 yesterday and the project no longer worked. The include files are still there, so are the dlls. The environment settings have not changed.
I tried opening other OpenCV projects that I know also worked for sure before the update and I'm getting the same error so I know my it's most likely not my code.
Here are the errors I'm getting:
I'd really appreciate any help if possible. It was a huge hassle for me getting the environment running the first time and now for this to happen is insanely frustrating, I just really want to start worrying about the actual code instead of all these inconvenient problems that are stopping me dead in my tracks.
After the update, the project was targeted for Windows SDK version 10.0.16299.0 which was not found on my device.
I right clicked on the solution and clicked retarget solution and that fixed the problem.
Multiple times throughout the day, my Test Explorer window in Visual Studio 2017 is locking up. Whilst it doesn't crash VS, when affected I can't run any tests as none of the options are available when right clicking on a test....
I have a mixture of NUnit and SpecFlow+ tests in different projects. Cleaning and rebuilding the solution doesn't work, the test explorer window doesn't change. Attempting to use the 'NUnit test (click to run)' option also does nothing.
The only way to resolve this issue is to restart Visual Studio which is highly frustrating.
Anyone know what the issue could be?
Thanks
I was also facing the same issue, as a workaround I Unloaded my test project and then Reloaded back; then ran the test again. This time it refreshed the Test explorer :)
My VS version: VS Professional 2019 Version 16.9.6.
Note: I had to do this to all my Test projects.
I have had multiple issues with specflow+. In the end I uninstalled specflow+ and went with normal specflow. This solved many issues for me, including this issue. Hopefully it will work for you as well.
I am trying to build a MFC Windows Application with Visual Studio 2008 on Windows 7. I use the "Batch build" feature of Visual Studio to get both Release and Debug of several projects' outputs with only one-click.
The problem is: Frequently, after I instruct VS 2008, some minutes later VS closes its window without any explanation. I have already seach the Web about these things and it seems that nobody as an answer.
I cannot be more specific than this. VS simply closes and you will not get any information.
Thanks in advance,
Sérgio
The best answer I could give would be to contact Microsoft directly and let them know of your problem. If there is no error information, it could be that they are not handling an exception and the program is just closing instead.
Seems that installing the patch quoted on http://arstechnica.com/microsoft/news/2009/03/widely-reported-crash-in-visual-studio-2008-sp1-fixed.ars solves the issue.
How can I get Visual Studio to help me optimize my application, or tell me areas of slowness? Thanks
If you have Visual Studio 2013 Professional then you can use the Performance and Diagnostics hub: http://blogs.msdn.com/b/visualstudioalm/archive/2013/07/12/performance-and-diagnostics-hub-in-visual-studio-2013.aspx . This profiler is well integrated in the IDE and I've found it really quick and easy for spotting code hotspots.
If you have the super enterprise edition it's built in (but I haven't used it - and I think it's ability to profile unmanaged code is limited)
Otherwise see What's the best free C++ profiler for Windows?
As another suggestion, I have found the AMD CodeAnalyst a great companion. It integrates with VS2010 very well, and provides detailed breakdown of CPU time on a line-to-line basis. You can zoom in and out to see from a top-level to a function-level. Not to mention it even has in-line disassembly display if you need that extra bit of information!
Totally worth a try.
The Windows SysInternals website has a number of other useful utilities for network management, security, system information and more. Check it out. I’m sure you’ll find something of value.
Here is how it helped me:
Slow Visual Studio Performance … Solved!
I had an odd performance-related issue today. My Microsoft Visual Studio seemed to be taking far too long to perform even the simplest of operations. I Googled around and tried a few ideas that people had such as disabling add-ins or clearing Visual Studio’s recent projects list but those suggestions didn’t seem to solve the problem. I remembered that the Windows SysInternals website had a tool called Process Monitor that would sniff registry and file accesses by any running program. It seemed to me that Visual Studio was up to something and Process Monitor should help me figure out what it was. I downloaded the most recent version, and after fiddling around a bit with its display filters, ran it and to my horror, I saw that Visual Studio was so slow because it was accessing the more than 10,000 folders in C:\Users\krintoul\AppData\Local\Microsoft\WebSiteCache on most IDE operations. I’m not sure why there were that many folders and moreover, wasn’t sure what Visual Studio was doing with them, but after I zipped those folders up and moved them somewhere else, Visual Studio’s performance improved tremendously.
I am running Visual Studio 2005 on Windows XP. It crashes without any error, log or trace when I try to load the solution for our product that contains 362 projects. I don't think the size of solution (362) is a problem, because it works on my colleagues computers. There is no entry of this in Event Viewer.
Any help to locate root cause of the problem or any solution if known would be greatly appreciated.
Thanks,
Shashibhushan
Thanks Luke for your suggestion. When I debugged using windbg.exe, it became evident that the exception was being generated at the time of loading dll related to "VMDebugger - Visual Studio Integrated Virtual Machine Debugger". I disabled it from the Add-in Manager and now the solution is being loaded successfully and working fine. Thanks for all your suggestions.
Thanks,
Shashi
Just some general thougts:
Uninstall SP1 - i had several difficulties with it. I.e. i was unable to create a working x64 DLL using SP1
Try again on a different machine that so far does not have Visual Studio on it. So you know wheteher its a problem of the Machine, or maybe a general Problem of Visual Studio
Uninstall and reinstall Visual Studio.
EDIT:
If you started seeing these problems yesterday i would even more strongly suggest, to uninstall and reinstall VisualStudio as well as SP1.
Did you install any new software recently?