By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
432,508 Members | 1,856 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 432,508 IT Pros & Developers. It's quick & easy.

How to: create a silent install project for "All Users" in Visual Studio 2003.NET

P: 1
Instructions for creating a silent install project in Visual Studio.NET 2003 for "All Users".

1) Create a default setup project for your application using Visual Studio (File/New/Setup and Deployment Projects)
2) Add all your components and fully test your setup project using default setup dialogue especially selecting "All users" option in Application Location dialogue.
3) In Visual Studio 2003, highlight your setup project and right mouse click. Select View/User Interface
4) In the User Interface Tree, remove all the interface screens under the Start, Progress and End branches.
5) Save you solution and rebuild your deployment project.
6) All user interface is now removed from your setup project
7) Download the ORCA database editor from Microsoft's Website (this is part of the Microsoft Platform SDK Components for Windows Installer Developers (see http://windowssdk.msdn.microsoft.com.../ms708365.aspx).
8) Open the application .MSI file using ORCA
9) Open the "Property" table and add a row as follows: Property=ALLUSERS Value=2
10) Save the MSI File
11) If the Setup is now run by an Administrative Windows User, it will be installed for All Users in Silent Mode
Oct 9 '06 #1
Share this Question
Share on Google+
1 Reply


P: 1
I have a Access Datafile installed along with the msi

when the mdb file is over written (with a new mdb with same structure but different data) its works fine in the installed user.

but when i log in as a different user and run the exe msi pops up and the database in
the original setup replaces the one i over write?

how to stop changing the key value (which i think is changed when i copy the new mdb file )

(i am using vb6 XP sp2)
Nov 20 '06 #2

Post your reply

Sign in to post your reply or Sign up for a free account.