Get your free Windows Vista and/or Office 2007 license here by entertaining yourself with videos!
When I upgraded to Windows Vista RTM I was reminded of the fact I already knew that Visual Studio 2005 has compatibility issues that so far have not been documented. After a week of tweaking a bunch of other things, I finally got around to firing up Visual Studio 2005 to see what is so incompatible.
The first concern I had was whether it would fail to fire up. No problems there. Then I created a Windows Forms app and tested CLR debugging. No problems there.
Next, I loaded the solution I’d been working on at work. This is a mix of class library projects and ASP.NET webs. Although I manually set up the main ASP.NET web project of interest on IIS 7 using the classic .NET 2.0 application pool, Visual Studio could not "mount" itself to IIS. Makes sense–IIS 7 breaks compatibility with IIS 6 components. There are backwards compatibility components you can install but AFAIK (but have not yet confirmed) these components are limited to workstation components for accessing other IIS 6 based servers.
All is not lost, you can still "mount" to the local file system directory and use the ASP.NET mini web server built into Visual Studio to debug. In theory.
However, given that our project files are shared on subversion (svn) with other team members who have no intention to use Windows Vista, I will not be able to get comfortable doing ASP.NET contributions on my laptop with the team.
Update: Nevermind. I’m debugging ASP.NET projects now. I’m not sure what I did between before and now, but I do know that among the requirements are 1) install IIS 6 compatibility components (which I already had), 2) enable Windows authentication on IIS, and 3) run Visual Studio as an Administrator.
I’m impatient, and I can’t wait two months for a delay of PowerShell RTM to show up on Windows Vista RTM (which I now have running solidly on my new $600 El Cheapo laptop).
Here’s how I got PowerShell running on Vista RTM. I have no idea whether it’s a stable manual install or whether tons of features are missing, all I know is that I got powershell.exe to give me a prompt. This is completely unsupported by Microsoft and might mess things up on your Vista RTM computer once Microsoft releases the official build–you will have to manually uninstall by doing these steps in reverse.
[UPDATE (12/17/2006):] Looks like someone found a better way.. http://gaurhothw.spaces.live.com/blog/cns!52B0837064D0B275!106.entry
This assumes that you are using Vista RTM 32-bit.
1. From a machine running XP SP2 with PowerShell RTM installed, copy the following directories with their contents to Windows Vista RTM.
– C:\Program Files\Reference Assemblies\Microsoft\WindowsPowerShell
NOTE: Some people are saying that the Reference Assemblies directory is invalid. Please view my 11/29/2006 comment in the comments (click on the Comments link). Someone found that they should be in C:\Windows\Assembly. I guess I found them in Program Files because I had previously installed a beta and that path got locked by way of a registry key.
2. Add the DLLs in the directory C:\Program Files\Reference Assemblies\Microsoft\WindowsPowerShell\v1.0 to the GAC by using "gacutil /i assembly.dll" for each DLL (replacing "assembly.dll" with the filename).
3. Download, extract, and execute the registry set from the URL below. This set is basically all instances of "PowerShell" I could find in my XP registry… unfortunately, it also includes some old Windows SDK CTP references that the Windows SDK CTP uninstaller did not clean out. No harm done, just adds useless junk to the registry.
4. Start PowerShell from C:\Windows\System32\WindowsPowerShell\v1.0\PowerShell.exe
If I forgot to list something in this list, you’re on your own.
I had added a shortcut to PowerShell on my XP SP2 QuickLaunch toolbar. I copied the shortcut file from the XP environment to my Vista environment (this brings me the width/height/color settings). Still to-do: Be sure to ngen all the assemblies for improved performance.