Hi

I have a winform app with sql server backend. How can I create a deployment
package which when run by the end user does the following;

1. Install front end vb winfrom app.
2. Install sql server express 2008.
3. Cerate backend database MyDatabase which relevant database objects;
tables, views, triggers, sps etc?

I need it to be as easy as possible for end user to install the app.

Many Thanks

Regards

"John" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi
>
> I have a winform app with sql server backend. How can I create a
> deployment package which when run by the end user does the following;
>
> 1. Install front end vb winfrom app.
> 2. Install sql server express 2008.
> 3. Cerate backend database MyDatabase which relevant database objects;
> tables, views, triggers, sps etc?
>
> I need it to be as easy as possible for end user to install the app.

The .NET installer technology allows you to

a) bootstrap installs (SQL Express, for example)
b) Run scripts

If you need something more configurable, you will have to go with another
installer technology or download tools to whack at the MSI to customize it.
I would suggest googling deployment, installer projects, and the like. You
also need to look at bootstrapping SQL Express; any decent site will also
show you how to check if it is installed so you don't try to install it
again.

--
Peace and Grace,
Greg

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

************************************************
| Think outside the box! |
************************************************

That brings up a question I've had. If Express (or full SQL Server) is
already installed, is it good practice to use the one that's already there,
or install a new Express instance?

I'm concerned about permission and login conflicts, and also the possibility
that the program that originally installed Express might uninstall it some
day.




"Gregory A. Beamer" <(E-Mail Removed)> wrote in message
news:0FDF8E2F-092A-476B-AC35-(E-Mail Removed)...
>
>
> "John" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Hi
>>
>> I have a winform app with sql server backend. How can I create a
>> deployment package which when run by the end user does the following;
>>
>> 1. Install front end vb winfrom app.
>> 2. Install sql server express 2008.
>> 3. Cerate backend database MyDatabase which relevant database objects;
>> tables, views, triggers, sps etc?
>>
>> I need it to be as easy as possible for end user to install the app.
>
> The .NET installer technology allows you to
>
> a) bootstrap installs (SQL Express, for example)
> b) Run scripts
>
> If you need something more configurable, you will have to go with another
> installer technology or download tools to whack at the MSI to customize
> it. I would suggest googling deployment, installer projects, and the like.
> You also need to look at bootstrapping SQL Express; any decent site will
> also show you how to check if it is installed so you don't try to install
> it again.
>
> --
> Peace and Grace,
> Greg
>
> Twitter: @gbworld
> Blog: http://gregorybeamer.spaces.live.com
>
> ************************************************
> | Think outside the box! |
> ************************************************

"Paul Pedersen" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> That brings up a question I've had. If Express (or full SQL Server) is
> already installed, is it good practice to use the one that's already
> there, or install a new Express instance?

I would say 9 times out of 10, you are better to just install a database,
but it may be more like 99 out of 100 or more.

> I'm concerned about permission and login conflicts, and also the
> possibility that the program that originally installed Express might
> uninstall it some day.

When you do an install with a database, ask for user credentials for install
and you can overcome the issues you talk about. With a previously installed
version of SQL or SQL Express, you can, with proper permissions, use the
attach stored procedure and actually ship with an MDB. This is faster than
using a full install script. You may still need the install script as a
backup (if nothing else, dump it so the user can install the database). If
you go that route, a config utility to change the connection string in the
config file.

--
Peace and Grace,
Greg

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

************************************************
| Think outside the box! |
************************************************