The tool you use to build your VSTO will have a large impact on the tool you use to build the setup application. I'm working an Outlook COM AddIn, now, using Visual Studio 2012.

The add-in installation may fail when installing the Visual Studio Tools for Office (VSTO), which is required to run the Microsoft Excel Data Everywhere add.

Using VS2012, the recommended solution is using the free InstallShield LE product. It's working fine for me within an organization of several hundred installations. Madagascar: Escape 2 Africa more. The MSI form is working best for me. I used the tips from this article: Using VS2010, you can try using the Windows Installer. My MSI setup asks no questions.

But distribution and installation is performed using another product by the IT department. It is that product that provides the 'quiet install' option. Hello Zoldello, There is no need to use InstallShield or any other 3rd party installers. The article in MSDN states the following (describes the required steps): You can create a custom installer for your Office solution, instead of using the setup program that’s created for you when you publish the solution. For example, you could use a logon script to start the installation, or you could use a batch file to install the solution without user interaction. These scenarios work best if the prerequisites are already installed on end-user computers. As part of your custom installation process, call the installer tool for Office solutions (VSTOInstaller.exe), which is installed in the following location by default:%commonprogramfiles% microsoft shared VSTO 10.0 VSTOInstaller.exe If the tool isn't in that location, you can use the HKEY_LOCAL_MACHINE SOFTWARE Microsoft VSTO Runtime Setup v4 InstallerPath or HKEY_LOCAL_MACHINE SOFTWARE Wow6432Node Microsoft VSTO Runtime Setup v4 InstallerPath registry key to find the path to that tool. You can use the following parameters with VSTOinstaller.exe.

/Install or /I Install the solution. You must follow this option with the path of a deployment manifest. You can specify a path on the local computer, a universal naming convention (UNC) file share, or an HTTP/HTTPS website.

You can specify a local path ( C: FolderName PublishFolder), a relative path ( Publish ), or a fully qualified location ( ServerName FolderName or ServerName/FolderName). /Uninstall or /U Uninstall the solution. You must follow this option with the path of a deployment manifest. Download Film Irani Gashte Ershad here. You can specify a path can be on the local computer, a UNC file share, or an HTTP/HTTPS website. You can specify a local path ( c: FolderName PublishFolder), a relative path ( Publish ), or a fully qualified location ( ServerName FolderName or ServerName/FolderName). /Silent or /S Install or uninstall without prompting the user for input or displaying any messages.