i am using visual studio 2015. i want a debugger that can support scripting, for example when hit the first break point 1 it can set another break point according to the value of a local variable.
can it be done with visual studio debugger?
and i am trying to use Microsoft windows debugger with visual studio 2015. According to Microsoft's document, visual studio has support Microsoft windows debugger from visual studio 2012.
Then i choose DEBUG -> Attach to process, but no "windows user mode debugger" transport ?
Related
How can i debugging VB6 project and its classes from attached process by using the Visual Studio 2017 and above version,
I am using visual studio 2017.
The configuration window image. Just click on it.
I upgraded C++ projects from Visual Studio 2010 to Visual Studio 2015, but it's still showing (Visual Studio 2010) in the Solution Explorer.
Please inform me if there is any change I need to do to solve this error.
This is displayed in the Solution Explorer:
This is not an error, it simply means that the project is using the toolkit that came with Visual Studio 2010. This doesn't prevent your projects from being compiled however.
To upgrade the project to the Visual Studio 2015 toolkit right click on the projects showing (Visual Studio 2010) and select the desired toolkit under General->Platform Toolset.
I have C++ VS2008 project and my lovely IDE VS13. How can I work into VS13, but compile and debug project like in would be VS08. When I open VS2008 *.sln files that wrote to me about one-way upgrade, and how you i guess you understand, project after open in vs2013 don't open in vs2008.
For now, I use VS13 like notepad then copy all files text to alt+tab opening VS 2008 IDE and there are run project. And again work in VS13.
Based on Microsoft product lifecycle policies,
https://support.microsoft.com/en-us/lifecycle/search?sort=PN&alpha=Visual%20Studio&wa=wsignin1.0
Visual Studio 2008's mainstream support ended in April 2013, while Visual Studio 2013 was released in Jan 2014. That means Visual Studio 2013 will not support Visual Studio 2008 bits, so not a surprise if native multi targeting does not show v80.
I don't think you can easily get side by side, as VS2008 is too old, and its C++ project is not even MSBuild script. Once converted to VS2013, there is no way back.
Why cannot you just let VS2008 go? I guess that's why you get so many down votes.
You can't convert the solution to Visual Studio 2013 and still open it in Visual Studio 2008. You can, however, tell Visual Studio 2013 to use the Visual Studio 2008 compiler.
To do that, convert your solution to Visual Studio 2013 (don't forget to keep a copy of the original file, just in case), then open the project properties, go to the General options and select the Visual Studio 2008 platform toolset.
I've installed x64 version of remote debugging components for Visual Studio 2015 on my Surface Pro 3 with Intel Core i3 CPU and recently updated to Windows 10 Pro Insider Preview x64.
When I'm trying to debug remotely simple universal application from Visual Studio 2015 RC (development machine runs Windows 8.1 Pro) I'm having this error in the output window:
Error: Unable to connect to the Microsoft Visual Studio Remote Debugger named '192.168.1.2:4020 (hosthame)'. The remote debugger is older than this version of Visual Studio 2015 RC, and Visual Studio is no longer compatible with it. Please upgrade your remote debugger to match Visual Studio.
Also there are records of failed attempt to connect in the main (log) window of Remote Debugging Monitor.
So, is there any "more updated" version of remove debugger component for Visual Studio 2015 RC then the current one I'm using, which, btw, has version 14.0.22310.1 and was "built by: DP" (have no idea what does it mean)?
Or any thoughts about other ways to workaround this issue?
I'm looking into installing Visual Studio on the Surface directly, but would like to avoid it if possible.
OK, I'll google next time harder - Remote Tools for Visual Studio 2015 RC (this link is no longer available, please use the links bellow).
Update (2016-06-28)
Remote Tools for Visual Studio 2015 Update 3:
Download (this link is no longer available, please use the links bellow)
Update (2016-09-28)
x64 - Remote Tools for Visual Studio 2015 Update 3
x86 - Remote Tools for Visual Studio 2015 Update 3
ARM - Remote Tools for Visual Studio 2015
Sevenate, your latest link is for the 2013 and not the 2015. Your second link still works, people just have to go to:
Tools for Visual Studio 2015->Remote Tools for Visual Studio 2015 and download the one for Update 3. I hope this helps
I want to skip debugging all of std:: namespace C++ by default, without code window changing to std:: code , authored by Microsoft as xstring . This question is similar to :
How to skip common classes in VS 2008 when stepping in? and
Auto-skip STL functions during step-by-step debugging in MSVC++2010 .
The only difference is that their solution are for visual studio 2008 and 2010. I tried it myself , and it works on visual studio 2010, but I want to do it on visual studio 2013. The same solution doesn't work on visual studio 2013. I tried changing all values in registry equal to :
_RTC_CheckEsp
to
std\:\:.*=NoStepInto
, some of these were values were for visual studio 12.0 ( which is visual studio 2013) , but after restarting visual studio 2013, nothing changed. On the contrary this works on Visual Studio 2010. "Just My Code" option is turned on.
As Hans Passant said, Edit the .natstepfilter files to add exclusions.
create a new file for example nostd.natstepfilter and write in it as in Has the VS2012 NativeDE\StepOver registry entry that prevents step-into for specific functions changed format?
<?xml version="1.0" encoding="utf-8"?>
<StepFilter xmlns="http://schemas.microsoft.com/vstudio/debugger/natstepfilter/2010">
<Function><Name>std::.*</Name><Action>NoStepInto</Action></Function>
</StepFilter>
For a 64-bit windows, move the file to :
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Packages\Debugger\Visualizers
while for a 32-bit windows to:
C:\Program Files\Microsoft Visual Studio 12.0\Common7\Packages\Debugger\Visualizers
or whatever you customized you installation to. Please note that natstepfilter does not work in mixed mode (mixing native and managed code). Ensure that your project debugging settings is set to Native only