About Windows Installer, the .NET Framework, and Visual Studio.
We have released a new revision of the July 2012 Update for VS2012 RC. This update replaces – or supersedes – the previous update, which means the download link is the same. We have retained the previous packages that VSUpdate installs – or chains – to support customers who may still require source packages when repairing Visual Studio 2012 RC or uninstalling VSUpdate RC.
We have also updated the previous KB2703187 article with the changes made in this re-release.
Should you have any problems installing the new revision July 2012 Update for Visual Studio 2012 on RC (v11.0.50522.1) please download and run our log collection utility and visit our forum or file a bug on Microsoft Connect.
But didn’t you just release the July 2012 Update?
Yes, but while we have been testing our new quarterly updates internally and have already released VSUpdate for VS2012 Beta and RC, we wanted to gather as much feedback from our customers as possible. Shipping the first version was planned well in advanced and was already in production when we started planning for this re-release, and we realized this is a good opportunity to test the production systems, the toast notification, and gather feedback.
And even though this is a revision of the July 2012 Update, the production process and end user experience are nearly identical to producing and installing the next quarterly update.
After installing this update it is no longer possible to launch *.vsix setups because it has destroyed this registry value
HKCR\VisualStudio.Launcher.vsix\Shell\Open\Command which now only is "" "%1"
instead of "C:\Program Files (x86)\Common Files\Microsoft Shared\MSEnv\VSLauncher.exe" "%1"
And also the DefaultIcon entry now is ",-221" instead of
"C:\Program Files (x86)\Common Files\Microsoft Shared\MSEnv\VSFileHandler.dll,-221"
@Andre, please download and run http://aka.ms/vscollect, then file a bug on connect.microsoft.com/visualstudio and attach the output (by default, %TEMP%\vslogs.cab) to the bug.
Also, please include the following to help us diagnose this since we've not seen this.
1. Did you have previous pre-releases (like Beta) installed?
2. Did you have previous VSUpdates installed (either Beta or the first RC update)?
3. What other VS products did you have installed (2012 or even older versions)?