Windows Virtual PC & Visual Studio .NET 2003
I have stumbled across some rather large bugs in Windows Virtual PC, and am wondering where to submit a bug report. The bugs are pertain to mobile device development in VS.NET 2003 for devices running Pocket PC 2002. VS.Net 2003 will install in Windows 7 but will not see my Pocket PC since I cannot use ActiveSync; So I turned to Virtual PC. here is a list of the bugs I have found: when I try to deploy my project to a device emulator, I get an error saying I cannot run an emulator in an emulator (with a rather irritating message saying, and I quote, "you just had to try, didn't you?"). I have to be running in full desktop mode because the option to connect a USB device to the virtual machine is only available in that mode. and I have to keep my projects saved on the virtual machine because I get an error saying I cannot save a project over a network connection.
May 29th, 2009 11:08pm

You do not have to be in full screen mode to connect a USB device. I often attach a USB device while windowed. Maybe if you turn off the "Enable at startup" for Integration Features.You can attach a USB memory device or Hard drive and see if that can be used to save projects to.
Free Windows Admin Tool Kit Click here and download it now
May 30th, 2009 2:23am

Disabling Integration Features at startup isn't working for me, to get ActiveSync to see my device I have run in full desktop and sellect "USB -> Unnamed Device Attach" (unnamed device is my HP Jornada Pocket PC).
May 30th, 2009 7:52am

Ok, now I understand, you wanted to run Visual Studio as a virtual App on your host machine.Visual Studio 2008 can run a pocket pc emulator while Visual Studio itself is running inside of a virtual machine.
Free Windows Admin Tool Kit Click here and download it now
May 30th, 2009 9:51am

No, I can't do that. All the devices I code for are Pocket PC 2002, VS 2008 won't compile/emulate for that. If I was just able to use ActiveSync instead of the Mobile Device Center, I would be able to just install VS.net 2003 in 7 and wouldn't have to deal with the Virtual PC. Also I have found another bug/problem with Virtual PC: I was installing some more software on the Virtual PC today and I was prompted to insert the Windows CD, as far as I can tell there is no CD image available short of buying a copy of windows. PS - is this proper place to report these bugs, or is there a separate forum/feedback method I should be using.
June 2nd, 2009 7:08am

Also I have found another bug/problem with Virtual PC: I was installing some more software on the Virtual PC today and I was prompted to insert the Windows CD, as far as I can tell there is no CD image available short of buying a copy of windows. You probably should start a new topic on the problem of software prompting to insert the Windows CD, becasue I think your question is too buried away for others with an answer to see it.I have a HP Jornado 540 that I will be experimenting with, now that I have it charged up. I have newer pocket PC devices that I use regularly, 2002 and 2003SE.I think I own a copy of VS.net 2003. I own all previous versions of Microsofts "Visual" software development software including the very first one.
Free Windows Admin Tool Kit Click here and download it now
June 2nd, 2009 8:50am

I slip streamed SP3 into a copy I have of Windows XP SP2 and I was able to use that disk for when prompted to insert the Windows CD.I could not install Visual Studio .NET 2003 however into Virtual XP, got a internal error message and the install was rolled back.So I made my own Virtual Windows XP (from a liscenced copy, for dev purposes,from my MSDN Professional subscription) and am now successfuly installing Visual Studio .NET 2003.
June 2nd, 2009 2:53pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics