Double-click the.exe file. Run the.exe file from a command line. If you run the.exe file from a command line, several switches may be available for use in the package. Note Not all switches may be available in all packages. To determine which switches are available in the package, use one of the following Help switches when you run the. Setup.exe and Update.exe Command-Line Parameters. InstallShield 2012 Spring. Setup.exe can accept a number of command-line parameters. Update.exe (available only for Basic MSI and InstallScript MSI projects) accepts nearly all of the same command-line parameters.
The Installer tool is a command-line utility that allows you to install and uninstall server resources by executing the installer components in specified assemblies. This tool works in conjunction with classes in the System.Configuration.Install namespace.
This tool is automatically installed with Visual Studio. To run the tool, use the Developer Command Prompt for Visual Studio (or the Visual Studio Command Prompt in Windows 7). For more information, see Command Prompts.
At the command prompt, type the following:
SyntaxParameters
Options
Additional Installer Options
Individual installers used within an assembly may recognize options in addition to those listed in the Options section. To learn about these options, run InstallUtil.exe with the paths of the assemblies on the command line along with the
/? or /help option. To specify these options, you include them on the command line along with the options recognized by InstallUtil.exe.
Note
Help text on the options supported by individual installer components is returned by the Installer.HelpText property. The individual options that have been entered on the command line are accessible programmatically from the Installer.Context property.
All options and command-line parameters are written to the installation log file. However, if you use the
/Password parameter, which is recognized by some installer components, the password information will be replaced by eight asterisks (*) and will not appear in the log file.
Important
In some cases, parameters passed to the installer may include sensitive or personally identifiable information, which, by default, is written to a plain text log file. To prevent this behavior, you can suppress the log file by specifying
/LogFile= (with no filename argument) after Installutil.exe on the command line.
Remarks
.NET Framework applications consist of traditional program files and associated resources, such as message queues, event logs, and performance counters that must be created when the application is deployed. You can use an assembly's installer components to create these resources when your application is installed and to remove them when your application is uninstalled. Installutil.exe detects and executes these installer components.
You can specify multiple assemblies on the same command line. Any option that occurs before an assembly name applies to that assembly's installation. Except for
/u and /AssemblyName , options are cumulative but overridable. That is, options specified for one assembly apply to all subsequent assemblies unless the option is specified with a new value.
If you run Installutil.exe against an assembly without specifying any options, it places the following three files into the assembly's directory:
Installutil.exe uses reflection to inspect the specified assemblies and to find all Installer types that have the System.ComponentModel.RunInstallerAttribute attribute set to
true . The tool then executes either the Installer.Install or the Installer.Uninstall method on each instance of the Installer type. Installutil.exe performs installation in a transactional manner; that is, if one of the assemblies fails to install, it rolls back the installations of all other assemblies. Uninstall is not transactional.
Installutil.exe cannot install or uninstall delay-signed assemblies, but it can install or uninstall strong-named assemblies.
Starting with the .NET Framework version 2.0, the 32-bit version of the common language runtime (CLR) ships with only the 32-bit version of the Installer tool, but the 64-bit version of the CLR ships with both 32-bit and 64-bit versions of the Installer tool. When using the 64-bit CLR, use the 32-bit Installer tool to install 32-bit assemblies, and the 64-bit Installer tool to install 64-bit and Microsoft intermediate language (MSIL) assemblies. Both versions of the Installer tool behave the same.
You cannot use Installutil.exe to deploy a Windows service that was created by using C++, because Installutil.exe cannot recognize the embedded native code that is produced by the C++ compiler. If you try to deploy a C++ Windows service with Installutil.exe, an exception such as BadImageFormatException will be thrown. Celine dion music free download. To work with this scenario, move the service code to a C++ module, and then write the installer object in C# or Visual Basic.
Examples
The following command displays a description of the command syntax and options for InstallUtil.exe.
The following command displays a description of the command syntax and options for InstallUtil.exe. It also displays a description and list of options supported by the installer components in
myAssembly.exe if help text has been assigned to the installer's Installer.HelpText property.
The following command executes the installer components in the assembly
myAssembly.exe .
The following command executes the installer components in an assembly by using the
/AssemblyName switch and a fully qualified name.
The following command executes the installer components in an assembly specified by file name and in an assembly specified by strong name. Note that all assemblies specified by file name must precede assemblies specified by strong name on the command line, because the
/AssemblyName option cannot be overridden.
The following command executes the uninstaller components in the assembly
myAssembly.exe .
The following command executes the uninstaller components in the assemblies
myAssembly1.exe and myAssembly2.exe .
Because the position of the
/u option on the command line is not important, this is equivalent to the following command.
The following command executes the installers in the assembly
myAssembly.exe and specifies that progress information will be written to myLog.InstallLog .
The following command executes the installers in the assembly
myAssembly.exe , specifies that progress information should be written to myLog.InstallLog , and uses the installers' custom /reg option to specify that updates should be made to the system registry.
The following command executes the installers in the assembly
myAssembly.exe , uses the installer's custom /email option to specify the user's email address, and suppresses output to the log file.
The following command writes the installation progress for
myAssembly.exe to myLog.InstallLog and writes the progress for myTestAssembly.exe to myTestLog.InstallLog .
See also
Active6 months ago
What's the minimum amount of software I need to install to get the 'tf.exe' program?
John MacIntyre
10.5k1010 gold badges6060 silver badges9999 bronze badges
213897213897
68633 gold badges1111 silver badges1616 bronze badges
8 Answers
You need to install Team Explorer, it's best to install the version of Team Explorer that matches the version of TFS you are using e.g. if you're using TFS 2010 then install Team Explorer 2010.
2012 version http://www.microsoft.com/en-gb/download/details.aspx?id=30656
2013 version http://www.microsoft.com/en-us/download/details.aspx?id=40776
You also might be interested in the TFS power tools. They add some extra command line features (using DLeh
tfpt.exe ) and also add some extra IDE features.
17.5k1111 gold badges6565 silver badges9696 bronze badges
James ReedJames Reed
I'm in a virtual machine, and am trying to keep my VHD as small as possible, so I find Team Explorer is a really heavyweight solution (300+ MB install). As an alternative, I've had some luck copying a minimal set of EXEs/DLLs from a Team Explorer installation to a clean machine (.NET 4.0 is still required, of course).
I've only tried a handful of operations so far, but this set of files (about 8.5 MB) has been enough to get basic source-control functionality via tf.exe:
Install Exe Command Line Options
(It should go without saying that this is a completely unsupported solution, and it doesn't free you from the normal TFS licensing requirements.)
Depending on the operations you perform, you may find that additional DLLs are required. Fortunately, tf.exe will produce a nice error message telling you exactly which ones are missing.
ijprestijprest
4,13011 gold badge1515 silver badges1212 bronze badges
In Visual Studio 2017 & 2019, it can be found here :
-Replace {YEAR} by the appropriate year ('2017', '2019').
-Replace {EDITION} by the appropriate edition name ('Enterprise', 'Professional', or 'Community')
FredericFrederic
1,09411 gold badge99 silver badges2727 bronze badges
There is a Java TFS client in the Team Explorer Everywhere installation (together with an Eclipse plugin). Look at http://www.microsoft.com/en-us/download/details.aspx?id=30661
MartinMartin
Visual Studio 2017 Team Explorer
According to https://blogs.msdn.microsoft.com/bharry/2017/04/05/team-explorer-for-tfs-2017/ you can now download it separately from Visual Studio via this link:
oleschrioleschri
For reference: these are the required DLLs for Visual Studio 2017 (as did @ijprest for the VS 2010)
They will be in my base VM image. I'm going to use it to pull the latest deployment scripts from VC to a temporary local workspace folder when installing a new server.
(Sorry to post this as an answer, but I don't have enough reputation to comment, which I believe it should have been)
Bert Van LandeghemBert Van Landeghem
You can also try TFS CLI for Node.js which is a cross-platform CLI for Microsoft Team Foundation Server and Visual Studio Team Services.
Mark GMark G
The tf.exe command line is included in the VSTS agent package in folder externalsvstsom.
Jules ClementsJules Clements
Not the answer you're looking for? Browse other questions tagged tfsinstallcommand-line-interfacetf-cli or ask your own question.Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |