Probably the most widely used developer tool is Visual Studio, and for that reason Parallels Desktop for Mac Pro Edition includes some special integration with Visual Studio. In this blog post I will describe and demo this integration.
VisualGDB features an open-source TFS plugin for easy out-of-the-box building of VisualGDB projects. Simply install the plugin to your TFS build server and build Make, CMake, or QMake-based VisualGDB projects easily and automatically with no need to install a separate instance of Visual Studio. I followed all the necessary steps as descripted in the Plugin Apps Developer Guide document to debug a plugin into Visual C++: Specify the Acrobat plug-ins directory under the link| output tab in the Project settings dialog box. Specify the Acrobat or Adobe Reader executable under the executable for debug session in the Project settings dialog box.
When the Parallels Tools for Parallels Desktop Pro Edition are installed in Windows, a Visual Studio plug-in, VMDebugHelper.vsix, is placed in the DevTools folder in the Parallels Tools folder in Windows. (See Figure 1.)
To install this plug-in, all the user must do is double-click on this file when Visual Studio is running.
This plug-in simplifies the use of remote debugging. In this context, “remote debugging” means debugging a program running in another virtual machine (VM) while you’re running Visual Studio and developing an app in a VM.
This plug-in installs a new menu in Visual Studio. (See Figure 2.)
Figure 2: The Parallels remote debugging menu in Visual Studio.
In this figure, I have the choice of the four currently running VMs: Windows XP, Windows 10, Windows 8.1 Pro, and Windows 7. The following 30-second video shows a remote debugging session of a small console application in the Windows 8.1 VM:
In the video, since the console application will run in the Desktop side of Windows 8.1, I first switch to the Desktop side. Then, in Visual Studio where I already have the console application project open and a breakpoint set in the code, I start a remote debugging session in Windows 8.1 Pro.
The necessary network connections are then established and the console application is launched in Windows 8.1. The breakpoint is reached, stepped over, and the console application runs to completion.
This type of remote debugging has three benefits for the developer:
Benefit 1:
Debugging can be done in a different OS than the OS in which development takes place. In Figure 2 and in the above video, I could have done the debugging in any one of four different OSes.
Visual Studio On A Mac
Benefit 2:
If the application which is being debugged were to crash (or even crash the OS), that crash is confined to the remote OS. My work in Visual Studio is safe.
Microsoft Visual Studio Community For Mac
Benefit 3:
Although not shown in this video, Parallels Desktop Pro Edition also enables the developer to simulate the network speed and even introduce network instabilities in the form of dropped packets.
If the application being debugged relied on networking, as is the case with Azure and many other technologies today, the application can be tested in a low bandwidth scenario and with varying amounts of network noise. (This network conditioning has been the subject of another blog post.)
We’re looking forward to adding even more integration with other development tools in Parallels Desktop Pro Edition. Let us know the tools you would like to see Parallels Desktop Pro Edition work closely with in a comment, or reach out to us on Facebook or Twitter.
Visual Studio
Need Microsoft Windows operating system to get started with Visual Studio? Buy directly below: