Visual Studio 2012 XML IntelliSense for URL Rewrite 2.0

Problem:
I am working on a web-project within VS2012. I was trying to implement url-rewriting as described at cache busting in ASP.NET by Mads Kristensen. I was running into the problem that VS2012 didn't recognize the tag inside the .
I got it to work/function (thanks to ScottGu's blogpost) after installing the URL Rewrite Extension on IIS7.x.
So far so good, but VS2012 intellisense still didn't recognize the tag.
Solution:
I searched around and found the post http://ruslany.net/2010/04/visual-studio-xml-intellisense-for-url-rewrite-2-0/ on RuslanY Blog. Unfortunately, the script didn't work on VS2012. Even changing a part of the code to var vs9CommonTools = shell.ExpandEnvironmentStrings( “%VS110COMNTOOLS%” );
However, a guy named Michal A. Valášek created an updated js script to get it to work on VS2012.
So I put the pieces together for your convenience, you can download it here (I called it rewrite2.1_vsintellisense). Note this script is just for VS2012! Just unpack the zip file, run the commandline window as administrator (elevated privileges), and execute the script file with cscript UpdateSchemaCache.js
Happy programming!

Visual Sourcesafe 2005 on Windows 8 64-bit

Problem:
I was running into problems when I tried to install Visual Sourcesafe 2005 (VS2005) on Windows 8 (64-bit) environment. And yes, I know, Sourcesafe is out-dated, but I still have to use it :(.
Anyway, I searched around but didn't find a solution. So I tried it myself to work something out, and with luck (and it is actually something stupid easy...)
Solution:
Just start the setup.exe of vs2005. You will run into the window 'Program Compatibility Assistant' (PCA), click on the option 'Run the program without getting help'.
You will get this PCA-window a couple of times, just continue clicking 'Run the program without getting help'. Finally you get in the ordinary installation procedure of VS2005 and you can install it as normal.
Once installed, it just works fine!

Edit: If it doesn't work, just verify if .NET framework 2.0 and 3.5 are installed (thanks Suren!)

Happy programming folks!