I had a little trouble getting Virtual PC 2007 to recognize my host machine's wireless network device. I don't know if you need to install drivers for it on your Virtual Machine instance, but i did it anyway. After I did that, the wireless device still wouldn't show up under settings.

So looking further, I found out there is a setting to specify the number of network devices that the virtual machine has access to. Go into the settings for you virtual machine, and under "Networking", set "Number of network adapters" to 2. Then set "Adapter 1" to your wireless network card, and "Adapter 2" to your LAN card. Start the virtual machine, and you should be good to go.

If you are only using a wireless connection, then you might get a message saying the LAN connection is not working. Simply disable it in Control Panel -- network settings, leaving only the wireless connection enabled, and you're good to go.

So you want to setup ASP.NET 2.0, Visual Studio 2005, and IIS7 on Vista Home Premium.

I don't want to repeat what someone has done a fantastic job of already, so here is a great article that covers quite a broad range of different scenarios:
http://learn.iis.net/page.aspx/431/using-visual-studio-2005-with-iis-70/

The article mentions one of the issues I had when trying to debug my web site application using Visual Studio 2005 against IIS7 (as opposed to the default ASP.NET web server) on Vista Home Premium. The error message displayed is:

Unable to start debugging on the web server. Debugging failed because integrated Windows authentication is not enabled. Please see Help for assistance.

The article mentions the following hotfix:
http://support.microsoft.com/kb/937523

One issue the article doesn't cover is when you try to view your site in a browser against IIS7 and get an error message similar to this:

CS0016: Could not write to output file 'c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\application1\c11b43f6\cf3ec03\rizcntet.dll'. The directory name is invalid.

The following KB article has the fix:
http://support.microsoft.com/kb/825791
Even though the article says it applies to .NET 1.0 and 1.1, it works fine with 2.0. On the step where it says to...

Grant full permissions on the Temp folder to the aspnet user account in .NET Framework 1.0 or to the NETWORK SERVICE user account in .NET Framework 1.1.

...use the NETWORK SERVICE user.

Hope this helps someone out there. It took me a little while to find the fix for that last issue.

While working on an XNA game engine, I started making a map editor for my tile engine. I wanted to use a winform app for it, so with a quick web search I found this winform sample on creators.xna.com.

After downloading the sample project, it comes with instructions in an html file on how to set up your own project using some of the files from the sample. It's fairly straightforward, however there were a couple of issues I ran into that aren't mentioned in the instructions. (Note: This might be related to Vista or Visual Studio 2005 Standard, since that is what I'm using.)

Error: Cannot find file Microsoft.Xna.Framework.dll

The big issue they don't mention is that if you reference the x86 version of the XNA Framework dlls, you also have to set your platform target to x86, otherwise you get an error message saying that Microsoft.Xna.Framework.dll cannot be found upon closing the winform. (You also won't see any textures being rendered correctly in the winform.)

In order to change the platform target to x86, select your winform's project and go to it's properties. Then under the "Build" section, change "Project Target" to x86.

My XNA control disappears from the designer after I Build my project

The other issue that threw me off a bit is that after you've added your custom control (that contains your XNA drawing functionality) to the winform, whenever you build the project and the form designer is open within visual studio, your custom control will disappear in the designer.

I don't know of a fix for the issue, but the workaround is to simply close and reopen the winform designer, and it should display again.