none
Installer RRS feed

  • Question

  •  

    Can some parts of the installation run without windows installer? E.g. InstallShield or some custom .net application.

    Tuesday, October 2, 2007 6:33 AM

Answers

  • No, Installer must use Windows Installer as per logo requirements. However multiple msi files can be bundled together using a bootstrapper. As per my knowledge, InstallShield also creates Windows Installer as output. So, one should be able to use Windows Installer created by InstallShield too.

     

    - Amitava

    Partner Technical Consultant, Microsoft.

    Tuesday, October 2, 2007 3:00 PM

All replies

  • No, Installer must use Windows Installer as per logo requirements. However multiple msi files can be bundled together using a bootstrapper. As per my knowledge, InstallShield also creates Windows Installer as output. So, one should be able to use Windows Installer created by InstallShield too.

     

    - Amitava

    Partner Technical Consultant, Microsoft.

    Tuesday, October 2, 2007 3:00 PM
  • We have a .Net 1.1 web-application developed using Visual Studio 2003. For deployment in IIS, we used the built-in installer-generator in Visual Studio 2003. This has worked well on Windows Server 2000/2003 and on IIS 5/6, but on IIS7 the installer did not manage to create a virtual directory.

     

    What is wrong? IIS7 or the generated installer?

     

    Wednesday, November 28, 2007 2:43 PM
  • i would recoment wix for a msi builder, u will need a month to use it well but will be worthy, office2007 and mssql use wix to build their msi, anyway this link is not wix exclusive

    http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg24601.html

    im in my way to test it, they say:

    I have implemented the configuration of IIS7 through xml manipulation of
    the applicationHost.config file.  All the IIS objects (app pools,
    applications, virtual directories etc) really just equate to xml entries
    in this file in this version of IIS.
    
    To achieve this, I copied the applicationHost.config, manually set up my
    web application through the Server Manager, and then did a file compare
    between the original applicationHost.config and the new one to see what
    IIS7 added for my application.
    
    Then, I used XmlConfig nodes to modify the file from the installation.
    
    The only issue you may run into is that the installation will need
    permissions to open and edit that file.
    Wednesday, February 11, 2009 11:08 AM