Note: this content originally from http://mygreenpaste.blogspot.com. If you are reading it from some other site, please take the time to visit My Green Paste, Inc. Thank you.

OK, so perhaps chaos is a bit of a harsh word here. But the clipboard was recently driving me nuts! All I was trying to do was copy some text to it, and the operation was failing. Of course, as it was an ad hoc app, I didn't have any kind of error handling. The app worked just fine on one system, but running the app on another system (a virtual machine) consistently resulted in failure to copy the text to the clipboard.

Ultimately, I was able to determine what process was preventing my app from putting data in the clipboard, but I haven't yet found a decent workaround for when the problem happens. It's not critical for me, as the act of copying the text to the clipboard is more of a nicety than a requirement.

Anyway, using P/Invoke and System.Diagnostics, I found that vmusrvc.exe - the Virtual PC "Virtual Machine User Services" - had the clipboard open. Using the timestamps from Process Monitor's Profiling Events

On top of releasing Windows Vista SP1 to a broad set of beta testers last week, the Windows Server Division also released Release Candidate 0 of Windows Server 2008. I used to work for a local ISP a few years ago and managed their Windows Server boxes running Windows Server 2003. I acquired skills in Active Directory management and IIS management - although very basic. I really wanted to try out the changes in IIS7 as well as changes coming to Active Directory in Windows Server 2008. I decided to fire up Windows Server 2008 RC0 in Virtual PC 2007.  

Windows Server 2008 in Virtual PC shows up on my home network as if it were an actual PC - with a real IP address and all.

I haven’t gotten around to testing Windows Server 2008 RC0 as a domain controller just yet. It currently sits on my home network serving as a web server (when fired up in Virtual PC). I used IIS7 to configure the server for “standard web hosting” - testing out using Microsoft Expression Web

…

On top of releasing Windows Vista SP1 to a broad set of beta testers last week, the Windows Server Division also released Release Candidate 0 of Windows Server 2008. I used to work for a local ISP a few years ago and managed their Windows Server boxes Read More……(read more)

• Microsoft Virtual PC 2007 Home
• Virtual PC 2007 Download (32 Bit and 64 Bit)
• Virtual PC Guy’s Weblog
• Using Microsoft Virtual PC 2007 for Application Compatibility (white paper)

Home

You know, there has been a lot of controversy lately (from developers I respect who should know better) about the news that Visual Studio .NET 2002/2005 will "mostly work but be unsupported" on Windows Vista. They claim that the answer "Just move your environment to Virtual PC and develop on VS.NET 2003 there" is unacceptable, claiming that virtualization is "slow, even on great hardware". Are the people complaining really going to be moving to Vista anyways? Or do they just like having stuff to complain about? Hmmm, I wonder…

First off, who is still developing on Windows XP in the first place? Most developers I know work on Windows Server 2003. It's faster, more responsive, and is more locked-down… plus you can develop and test on the same machine with IIS 6 built-in. You can say "well, my shop can't afford that many license of Windows Server", but every Microsoft shop should have at least one MSDN subscription. It's the single most cost-effective way to build testing environments.

But I digress. The bottom line is, if you're a develpment shop, and you're NOT using virtualization yet, you are wasting valuable time and money. How can I make such a bold and

…