09 December 2015

How to repack Visual Studio 2010 Express for SVCPACK installation

VS 2010 is the last for XP so I want to have convenient up-to-date package that I can slipstream into XP iso.
Firstly this post http://www.itninja.com/question/visual-studio-2010-express have all the ingredient for us to cook. Lets go!

- Extract all Ixp*.exe file with 7zip (ignore the warning).
- Make admin installer from each extracted vs_setup.msi (msiexec /a)
- Edit each of administrative version of vs_setup.msi with Orca:
  - Remove CA*LaunchCondition in all Install*Sequence tables (to allow running and updating)
  - Remove *SETUP entries from all Feature* tables (to remove copy of the whole cabinet installer)
  - Remove entries with CSETUPMM directory from Component table
  - Replace PIDKEY in Property table with your serial (without hyphens)
  - In Registry table find "UninstallString" (on first occurrence) and replace value of "SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\[ProductName]" with "MsiExec.exe /X[ProductCode] "also remove its "UninstallPath" entry
- Save your edited vs_setup.msi
- Now you can remove all files in root except vs_setup.msi and remove CSETUPMM folder from "Program Files\Microsoft Visual Studio 10.0"
- Apply all applicable updates (SP1, etc) into vs_setup.msi (use the *msp file from VS10SP1*.exe )

Beware about your OS situation (.NET version, MSI, etc) cause after this you're on your own.

In my test compressing all (C++, C#, VB, Web Developer and its dependencies) with 7zip produce just about 150MB! Quite a saving eh

- After merging patches we need to reset the package-code (Orca View > Summary) with the original one (and change the description as well if you wish)


  1. Visual Studio 2015 still supports Windows XP, you just have to set "Platform Toolset" to "v140_xp" :-)

    1. As I said in the article I want to slipsteam it into XP iso, I use XP and want the last VSX that run on XP not VSX that target XP :-)

    2. Okay, I see. Developing or building software on an end-of-life OS, which does *not* receive any security patches for about 2 years now and thus has many unfixed security vulnerabilities now (judging from all the vulnerabilities they fixed in the "supported" Windows versions during that time), doesn't seem like a good idea, though.

    3. I should have know that that was what's on your mind :)
      I could explain it why, but basically this post is made as side-effect of http://opensourcepack.blogspot.co.id/p/xp-last-resort_12.html I hope you don't misunderstand