Attention: We are retiring the ASP.NET Community Blogs. Learn more >

Using Windows Server 2003 As Dev

While trying to program ASP.NET, I used my copy of Windows Server 2003 Enterprise to make my laptop into one smoking loaded development machine.  And it was good.  But as soon as I tried to install the Virtual PC drivers (needed to run the pocket pc emulator), it failed, saying that the likely culprit was that I was not an administrator (I am).

Suffice it to say, I believe the Emulator Driver (Virtual PC Application Services), is fighting with Windows 2003. (Windows says that driver could not be found, after trying to run the “Smart Devices Emulator.msi” or Setup.exe, both in %VS.NET2003 Installation Directory%\CompactFrameworkSDK\ ConnectionManager\Bin\DriverInstall).

I really am stymied with this one.

4 Comments

  • So, why do you need the pocket pc emulator on the server? Did you install it as your dev machine's OS? If so, definately a bad idea (IMO). Win Server 2003 isn't meant to be a client OS, and lots of installs are going to fail for various reasons.

  • win2k3 rocks as a desktop. Best desktop OS currently available.

  • Jason,



    In spite of the troubles with doing so, I do as well use Win 2K3 as a desktop environemnt part of the time, and I find it to be fine. I am running both Virtual PC and the emulators that are installed with Visual Studio .NET 2003, and I did not encounter a problem. Hmm. I wonder why...

  • I find installing any kind of client s/ware on a server is asking for trouble in the long run, however as this is not a production server i am surprised to see you having problems at the install stages!!! hmm

Comments have been disabled for this content.