Using Virtual PC to test Visual Studio “Orcas”

As you may know, Microsoft provides now the CTPs and Betas of Visual Studio “Orcas” (currently Beta 1 at the time of this writing) in the form of virtual machines for Virtual PC, which is great to avoid a second computer or second partition to test it. If you are not very familiar with Virtual PC, as it is my case, you may find interesting some issues that you may encounter when using it:

  • If you are using Windows Vista as your host OS, you need Virtual PC 2007.
  • It is recommended that you change the memory of the virtual machine from the default 384 KB (IIRC) to something like 1024 MB or similar. I am using a Sony Vaio SZ3 with 2 GB of memory so it should run nice.
  • To allow mouse integration and shared folders between the host and guest operating systems, you need the Virtual Machine Additions, which I think that are installed by default with the supplied virtual machine. One thing that confused me a lot is that you can’t set shared folders until the virtual machine is running (the settings appear disabled otherwise). I thought that Virtual Machine Additions were not installed. It would be nice if Microsoft added a warning in the settings to inform that the virtual machine must be running. Otherwise you may think that the Virtual Machine Additions are not installed, which is the warning that appears in the explanation of the setting.
  • I have found that the contents of the subfolders of a shared folder were incorrect the day after setting the shared folder: when opening a subfolder, its contents were those of the previous subfolder. Quite strange, it seems a bug. I solved it reassigning the shared folder again.
  • The performance of the shared folder is quite bad, I am not sure how to improve it.
  • You may notice that the mouse cursor disappear as soon as the mouse enters a textbox, or, most importantly, the editor of a code window of VS. Although most mouses have a setting “Hide cursor while typing”, this setting is not the problem. After some investigation, it happens that the problem is the hardware acceleration of the video. You have to right-click on the desktop, select the “Properties” context menu, “Settings” tab, “Advanced” button, “Troubleshoot” button, and change the “Hardware Acceleration” slider from Full to one step less.I hope that some day this Troubleshoot dialog is no longer needed, it is the second time that I have to use it for display problems, and things should work fine without these tweaks.
  • In the March 2007 CTP the virtual machine did not use an undo disk. In the Beta 1 virtual machine, it does, which causes that the dialog that is shown when closing the virtual machine is even more confusing, since it shows a checkbox to commit the changes. Once you understand the dialog without undo disks (Save state, Shutdown, Turn off) and you understand the undo disk feature, all makes sense, but for beginners it is somewhat confusing.

I hope this helps to get you started when evaluating Visual Studio “Orcas” without being distracted by the Virtual PC stuff…

4 thoughts on “Using Virtual PC to test Visual Studio “Orcas””

  1. I tried decreasing the hardware accel and now the colors in the vpc are really messed up – nothing looks right. Just a warning to others that might try this.

  2. Hi there,

    I found another workaround which works very fine.
    Just get the cursors from your vista-system (i.e. “C:\Windows\Cursors”) and replace the I-Beam cursor of your current scheme in virtual pc with the cursor you copied from vista.

    It works without disabling the hardware-acceleration 😀

    Best regards,
    Waescher

  3. Thank you for the quick fix for disappearing cursors (knocking the acceleration down a notch).

    This was driving me crazy!

  4. Beautiful. Absolutely freakin’ beautiful. Thanks for helping fix the disappearing cursor. It was driving me crazy, too.

    Raz

Comments are closed.