Setup file options

[hamking01]

When creating a setup/deployment installer for an asp.net application can options be added to allow users to choose the back-end database and based on the selection use a certain connection string for the web.config file.

How do distributed applications setup the back end database? Or must it be installed sepeartely.

For example, if i was creating and selling a web application software. I want to allow users to choose either Access or SQL Server as the back-end db. Based on the selection the app would install using appropriate connection string.

How would this software setup the database. Or does the database need to be configured manually for each installation?

 

[jbenson001]

You would have to know a few things first:

For Access you would have to know the physical path of the .mdb file, and any user name and password.

Fro SQL server you would need to know the server name, database name, and user name and password.

Do you plan on letting them select these various properties and then constructing the connection string, or will you know the properties and then just select the connection string accordingly.

You could constuct the connection strings in the web.config ahead of time and use the approriate one. Or you could construct the connection strings and save them to the web.config. Either way, there are some things you need to know ahead of time. Basically, how dynamic do you want it to be.

Jim

 

[hamking01]

The application would be given away to allow users to install. I want to allow a few installation steps for the user as possible, so forget the sql server. Don't wanna deal with the security. With Access for example, it would create a new mdb file, with no security settings. How can I have the installation file install/create the db schema such as tables, queries etc...