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.
I have previously posted instructions for performing a silent installation for Visual Studio 2005 and the Visual Studio 2005 Express Editions. A customer read those previous blog posts and asked a follow-up question about how to perform a silent installation of Visual Studio 2005 Team Explorer, which is the client software needed to access Team Foundation Server.
Team Explorer setup is architected in a way that is similar to the Visual Studio 2005 Express Editions, but the silent installation instructions are a bit easier because unattended INI file creation was not specifically disabled in setup UI like it was for the Express Editions.
How to perform a silent install of Visual Studio 2005 Team Explorer
Here are the steps that you can use to perform a silent installation of Visual Studio 2005 Team Explorer:
Please note that the above steps are not documented with the product because this unattended mode is not officially supported. Unattended INI creation mode is not specifically blocked in the Team Explorer setup UI code, but it is also not an "official" feature, and as such has not been tested as thoroughly as other setup features. That being said, it appeared to work fine for me in the scenarios that I tried.
More in-depth details about Team Explorer silent installation
<update date="1/21/2010"> Fixed broken link to image. </update>
I am trying to install the Team Explorer silently on a terminal server. All components are going to be installed, but the team Explorer and the Office Plugins are not going to be installed. Does anyone know this problem?
Hi Alexander - I'm not sure I understand your question. Is your install failing, or are you trying to create a customized silent install that excludes some components? Can you please provide more detail about what you are trying to accomplish and what (if any) errors you're encountering?
Ok i proceed the following steps on the terminal server:
-Create an unattend installation via setup.exe /CreateUnattend
-change Actioninteger from 5 to 1 as described in this blog
-start unattend installation via setup.exe /UnattendFile
The setup runs install different parts of the Client like XMLParser, Premium Partner Edition, but the Team Explorer and the plugins are not going to be installed. No errors in the eventlog.
When i run the setup manually over the GUI, the installation in successfully and the Team Explorer and the plugins were installed.
Hi Alexander - I assume you are trying to change the ActionInteger values to help manage reboots like I described at http://blogs.msdn.com/astebner/archive/2006/03/17/554248.aspx. Is that accurate? If so, I'm not sure why those changes would cause Team Explorer itself to not install. Can you please zip and send me your original, unmodified INI file, your modified INI file and the log file from your attempted installation so I can take a look and see if I can figure anything out? You can send these items to Aaron.Stebner (at) Microsoft (dot) com.
This guide is intended to serve as a collection of links to articles, tools, tips and tricks that explain
I've tested your suggestion (But I use TE 2008) on my local machine (Don't have Visual studio. I'm going to install TE only) and found that if machine doesn't have "microsoft visual studio 2008 shell (integrated mode)" then the steps in your post won't work. I tested this on another machine that has "microsoft visual studio 2008 shell (integrated mode)", everyting is ok?
Do you have any suggesstion?
Hi Phanita - The steps in this blog post are for Team Explorer 2005, not 2008. I haven't tried the equivalent steps in Team Explorer 2008, so there is a chance it doesn't work the same way. I will try to make some time to try out the Team Explorer 2008 silent install scenario soon, but keep in mind that there is not an officially supported way of doing this, so even if we can come up with a way to get it to work, it will be "use at your own risk."
In the meantime, do you have any logs from the installation scenario that failed that we could use to try to narrow down the cause? There is a list of log files produced by VS 2008 setup in the blog post at http://blogs.msdn.com/astebner/archive/2007/07/31/4156781.aspx.