Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio
All postings are provided AS IS
with no warranties, and confer no rights. Additionally, views expressed
herein are my own and not those of my employer, Microsoft.
The following options can be used to download and assemble a folder structure that can be used to install one of the Visual Studio 2008 Express Editions.
Option 1: Download and burn or extract the CD image (easiest option)
The first, and easiest option is to utilize the Offline Install instructions for Visual Studio 2008 Express Editions page on the MSDN site. These instructions allow you to download an ISO file for a DVD image that contains all of the following Visual Studio 2008 Express Editions and their prerequisites and optional components:
Once you have downloaded the ISO file, you can either burn the image onto a DVD and then copy the contents to your local hard drive or extract the contents to your local hard drive directly using a tool such as IsoBuster.
Once you have copied the contents to a local hard drive, you can share out the folder on a network and install it from there if you choose to.
Option 2: Manually assemble the equivalent of the CD image (advanced option)
If you need to optimize bandwidth or for some other reason cannot use option 1, you can use some advanced steps to reverse engineer the VS 2008 Express Edition setup data files and manually download the individual pieces you will need to create a network installation point. If you use these steps, you can optimize your download size by only including a single Express Edition instead of all 4. You can include only the optional components you want to install (meaning you can skip SQL Express and MSDN if you choose to not install them during Express Edition setup). You can also optimize your download size based on the configuration of the machines you will be installing on. For example, if you know you will not need to install on any x64 systems, you can skip downloading the x64 components for SQL Express and the remote debugger. Also, if you know that the systems you will install on already have prerequisites such as Windows Installer 3.1 or the .NET Framework 3.5, you can skip downloading those components.
The following steps will allow you to manually assemble an installable layout for an Express Edition. In this example, I will use the Visual Web Developer 2008 Express Edition (English), but equivalent steps can be used for the other Express Editions and non-English languages as well. For other Express Editions, you will need to change the download location used in steps 1 and 5 below.
Windows Installer 3.1
Visual C++ Minimal Redistributable
.NET Framework 3.5
Remote Debugger (x64)
Windows SDK Express Tools for Web (only needed for Visual Web Developer Express Edition)
Windows SDK Express Tools for the .NET Framework (needed for Visual Basic, Visual C++ and Visual C# Express Editions)
Windows SDK Express Tools for Win32 (needed for Visual Basic, Visual C++ and Visual C# Express Editions)
Windows SDK Express Headers and Libraries (only needed for Visual C++ Express Edition)
Visual Studio Web Authoring Component (only needed for Visual Web Developer Express Edition)
SQL Server Compact 3.5 (needed for Visual Basic and Visual C# Express Editions)
SQL Server Compact 3.5 Design Tools (needed for Visual Basic and Visual C# Express Editions)
SQL Publishing Wizard (only needed for Visual Web Developer Express Edition)
SQL Server Express (x86)
SQL Server Express (x64)
Additional notes for non-English Express Editions
If you want to create an installable layout for a non-English Express Edition, you will need to use different URLs than the ones listed above. The URLs can all be assembled using the prefix http://go.microsoft.com and the data stored in the URL value for the section in the file baseline.dat that corresponds to the component in question.
In addition, you will also need to download the language pack for the .NET Framework 3.5 for non-English Express Editions. This can be done with the following steps:
.NET Framework 3.5 language pack (x86)
.NET Framework 3.5 language pack (x64)
Advanced note about setting default checked state for optional components
You can configure the default checked state for the SQL Server Compact 3.5, SQL Server Compact 3.5 Design Tools, MSDN Express, SQL Express and Silverlight 1.0 optional components using the DefaultSelected and WebDefaultSelected values in baseline.dat. Setting them to 0 will cause the setup UI to appear with the checkbox unchecked for the item in question, and setting them to 1 will cause the setup UI to appear with the checkbox checked for the item in question. The default selection state only applies to optional components for the Express Editions, so setting these values for components other than SQL Server Compact 3.5, SQL Server Compact 3.5 Design Tools, MSDN Express, SQL Express or Silverlight 1.0 will not have any effect.
PingBack from http://msdnrss.thecoderblogs.com/2008/03/14/how-to-create-an-installable-layout-for-a-visual-studio-2008-express-edition/
PingBack from http://msdnrss.thecoderblogs.com/2008/03/19/how-to-create-a-combined-network-install-point-for-all-visual-studio-2008-express-editions/
I previously posted an item describing how to create an installable layout for a Visual Studio 2008 Express
A while back, I posted a set of instructions for automating the install of Visual Studio 2005 Express
PingBack from http://msdnrss.thecoderblogs.com/2008/03/24/how-to-silently-install-the-components-included-with-the-visual-studio-2008-express-editions/