Visual Studio 2003 Setup Package Inquiry

DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 4 of 4

Thread: Visual Studio 2003 Setup Package Inquiry

  1. #1
    Join Date
    Apr 2007

    Visual Studio 2003 Setup Package Inquiry

    I'm not sure if this can be done and I've been searching the web for some time looking for some help with this.

    I created a setup package with 2003 and I want to run a second setup package during the installation. Is this even possible? If it is, how would it be done?

    Edit: A little more information on this issue: The second setup installation is for a USB driver. Basically we have an application that is being installed to monitor a portable power source, but we need to integrate the driver installation into the installation of our created application so that the driver installation setup package runs when the original setup package runs.
    Last edited by asull100; 04-11-2007 at 10:56 AM.

  2. #2
    Join Date
    Nov 2003
    Portland, OR
    It is possible, but you cannot do it using Visual Studio alone. You will need to edit the MSI file created by VS to include a Custom Action. To do so, you may use the Windows Installer Automation interface, or you may use Microsoft's Orca tool to edit the MSI interactively. For more information, see
    Phil Weber

    Please post questions to the forums, where others may benefit.
    I do not offer free assistance by e-mail. Thank you!

  3. #3
    Join Date
    Apr 2007
    I had an there no way to set a launch condition on setup 1 that looks for the driver file, and if there is a negative return, run setup 2 then continue to setup 1?

    BTW, thanks for your help, Phil.

  4. #4
    Join Date
    Mar 2005
    As Phil said, you are able to run setup2 during setup1 (called nested installation), but it's NOT recommended.

    There are many reasons not to use nested installation. Microsoft addresses some of the drawbacks here:
    But which I most concern is that nested installation does not provide the "real" picture to setup1.

    Take an example, if setup2 has bug and does not install the driver onto the machine properly (even it's finished "as normal"), setup1 will still assume the driver is installed and proceed. This can be dangerous.

    In my view, the most sensible way is to check the driver existence in setup1. If the driver does not exist, prompt the user to install the driver first and abort setup1.

    Don't try to make thing "over automatic" which is unmanageable.

Similar Threads

  1. Visual Studio 2005 Issue
    By Karl_Liberty in forum .NET
    Replies: 2
    Last Post: 01-04-2007, 08:53 AM
  2. Replies: 0
    Last Post: 05-28-2003, 10:34 AM
  3. Replies: 0
    Last Post: 05-20-2003, 07:06 AM
  4. ANN: Release of DeKlarit 2.0 for Microsoft Visual Studio .NET
    By Maria Jose Serres in forum dotnet.announcements
    Replies: 0
    Last Post: 02-19-2003, 02:54 PM
  5. YAG's public status report - March 7, 2002
    By Seth Grossman [MSFT] in forum vb.announcements
    Replies: 1
    Last Post: 03-13-2002, 07:32 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
HTML5 Development Center
Latest Articles
Questions? Contact us.
Web Development
Latest Tips
Open Source

   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center