I am using Visual Studio Premium 2013 Update 2 on a freshly installed (fast) machine with Windows 8.1 Update. Everything is running smoothly, only one thing bugs me:
Problem
When I debug a native C++ project (debug build) by going from line to line with F10 ("step over") it takes 1-2 seconds to go to the next line when I press the F10 key.
What I tried
I looked at several other questions related to slow debugging and made sure that neither of the following is not the reason in my case:
Everything is local (app and all data), no network shares involved
Disabling the Microsoft symbol server did not help
I only have a single breakpoint
Using the menu/toolbar instead of the keyboard does not make any difference
In the default configuration "edit and continue" is enabled, but apparently not for native code:
When I disabled "edit and continue" completely, F10 stepping became much faster (0.5-1 s). The speed is tolerable now. I had to restart Visual Studio after I changed the configuration to this:
Related
I'm trying to build and run a simple project in Visual Studio 2017 (C++) in x64 using the Local Windows Debugger. However every time I try to run it using the debugger I get this error.
This error doesn't show up when I change it from x64 to x86, but I need it to compile to x64. This has happened on both computers that I've tried it on, and seems to happen in every one of my projects. I've tried reinstalling Visual Studio already and nothing's changed. I've tried adding 'devenv.exe' as an exception to the Windows Firewall but no changes there either, even when I disabled the firewall completely. My antivirus isn't affecting it at all either: still happens when I disable it.
The application runs fine when I find it in the explorer and run it manually but then I don't have any debugging tools.
What am I doing wrong here, how do I make it build and run my project as x64?
I get this error every time I have an active VPN connection. If you use a VPN, try disconnect and see if the error disappears.
If you want to use a VPN, the solution (assuming you have Visual Studio 2017 Version 15.7 or later) is as follows:
Go to the Windows Start Menu and launch the “Developer Command Prompt for VS 2017 Preview”
Run: "%DevEnvDir%vsregedit.exe" set "%VSINSTALLDIR:~0,-1%" HKCU Debugger UseAnonymousPipes dword 1
Restart VS if it is already running
That solution is from this link to Microsoft.
I created a Visual Studio C++ project, write a game (about 10K-lines).
Yesterday, I compile and ran it in release mode, then I got some access violation error.
My program doesn't have any virus-like command, the closest one is just the array access,
so I think it came from array-index-out-of-bound.
Therefore, I aborted my program - using STOP button - and edit my code, test it again - F5 (release mode, not-optimized).
This happened around 10-20 times - crash & debug ; my happy life cycle.
When I shut down, Windows 7 created a popup error about access violation.
(It has sometimes happened before, but has never caused any serious long-term affect.)
Problem
Today, after I turned on the computer, it began to act strangely
Windows and Visual Studio start up a little slower. (I may be biased.)
Windows task bar (that has the start button) is quite non-responsive. (obvious, happen only once)
Visual Studio : some shortcuts (Ctrl K + Ctrl O to switch .cpp /.h) not work anymore except it open a file instead (look like it recognize only Ctrl O).
Visual Studio : I can't assign any shortcut that has 2 Ctrl button (e.g. Ctrl xxx + Ctrl xxx)
I test with on-screen keyboard, after a bit of testing, my computer crashed. (mouse cursor disappear)
After I turned on my computer again - avoid opening Visual Studio, my computer act as almost normal, but alt+tab not work anymore.
Note that I didn't install any new software in the last 7 days.
Question
Is it possible that bug / crash of my C++ program (always run within Visual Studio) can destroy some structure of Visual Studio or OS unintentionally?
If so, is there any setting of Windows / Visual Studio to prevent it?
In our company me and some of my colleagues switched from windows 7 do windows 10. All of us noticed the same bug in the Visual Studio 2013:
When the debugger hits the breakpoint and stay there, writing a text starts annoyingly lag anywhere (e.g. in visual studio, notepad, browser...). Everything else on PC works without lagging.
I also have noticed that it happens only if we debug the application which extensively use the GPU.
P.S. Yes we have an updated drivers for Nvidia.
I know there are several VS keyboard shortcuts for running unit tests, but the one I really can't find and would like is to be able to run the last executed test in debug mode.
Ctrl+R, L will repeat the last run, but not in debug mode.
If you are debugging a test, and it changes context to the code you are actually running, and then you stop the test, is there a way to start that test in debug mode again using just the keyboard?
I wanted the same thing.
Based on the technique found in the following post
Visual Studio 2012 debug tests keyboard shortcut
I searched for TestExplorer.DebugSelectedTests and assigned a shortcut key to it.
At least in VS2015 (and hopefully in VS 2013) even while debugging changes context to the code you are actually running. The test remains selected in the test explorer window. So, you can run your shortcut key combo and the test will debug again.
Hope this solves the problem for you too.
I know this question was for Visual Studio 2013, but got google go me here.
In Visual Studio 2019 is a shortcut for that Ctrl+R,D:
If you are using ReSharper, you can use Ctrl+U, D to rerun a test in Debug mode.
https://www.jetbrains.com/resharper/features/unit_testing.html
I have created a multi device hybrid project in Visual Studio 2013.
I am having a few major issues:
1) Changes to my scripts do not appear unless I completely rebuild the application when I am using Ripple to view the project.
2) Pressing F12 in the Chrome ripple window causes Visual Studio to stop running the application. This seems very strange. It's like if I were to quit debugging on a normal webapp.
Output shows The program '[1] http://localhost:4400/index.html?enableripple=cordova-3.0.0-NexusGalaxy: WebKit' has exited with code -1 (0xffffffff).
Has anyone had these problems or know what might be causing them?
Both of the behaviors you describe are expected. Ripple is not automatically refreshed when you save your changes so you will need to rebuild and deploy for it to pick up the updates. Since only one process can use the webkit debugging at once, the VS debugging session gets disconnected when you use the debugging tools in Chrome.