locked
Remote Debuggin with Visual Studio 2013 and Windows XP target machine? RRS feed

  • Question

  • We have upgraded from Visual Studio 2005 to Visual Studio 2013.

    Our target products run windows xp, and with Visual Studio 2005 we use remote debugger to debug.

    With Visual Studio 2013 we cannot install the remote debugger in the target machine with Windows XP, and this is a mayor requirement.

    We cannot migrate to newer version on windows in the target machine, so that is not an option.

    Our development laptops run windows XP, windows 7 and 8.

    Our applications are only Visual C++, no web, no java, just C and C++ using MFCs.

    What are we missing? Is there any way to remote debug a Windows XP target?

    Maybe installing an older version of the remote debugger?

     

    Tuesday, May 27, 2014 9:41 AM

Answers

  • We have upgraded from Visual Studio 2005 to Visual Studio 2013.

    Our target products run windows xp, and with Visual Studio 2005 we use remote debugger to debug.

    With Visual Studio 2013 we cannot install the remote debugger in the target machine with Windows XP, and this is a mayor requirement.

    We cannot migrate to newer version on windows in the target machine, so that is not an option.

    Our development laptops run windows XP, windows 7 and 8.

    Our applications are only Visual C++, no web, no java, just C and C++ using MFCs.

    What are we missing? Is there any way to remote debug a Windows XP target?

    Maybe installing an older version of the remote debugger?

     

    Hi,

    I am afraid that Remote Tools for Visual Studio 2013 don't support remote debugging on Windows XP, you could check Remote debugging of Differences between the toolsets in Configuring C++ 11 Programs for Windows XP

    Remote Tools for Visual Studio 2012 don't support remote debugging on Windows XP or Windows Server 2003. To debug an app while it's running on Windows XP or Windows Server 2003, you can use a debugger from an older version of Visual Studio to debug them locally or remotely. This resembles the experience of debugging an app on Windows Vista, which is a runtime target of the v110 platform toolset, but not a remote debugging target

    And you could use the way shared in this blog:

    Windows XP Targeting with C++ in Visual Studio 2012 - Visual C++ Team Blog - Site Home - MSDN Blogs

    Remote Debugging
    The Remote Tools for Visual Studio 2012 do not support remote debugging on an XP client. When debugging on Windows XP is required, it is recommended to use the debuggers of an older version of Visual Studio, such as Visual Studio 2010, for local or remote debugging. This is in line with the Windows Vista experience for Visual Studio 2012 RTM, which is a runtime target but not a remote debugging target.

    >>Maybe installing an older version of the remote debugger?<<

    That means we need to install the older version of Visual Studio in local machine too, and use that older version to remote debug.

    Regards. 


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    • Marked as answer by Carl Cai Wednesday, June 4, 2014 5:33 AM
    Wednesday, May 28, 2014 6:35 AM