create setup file in vb.net 2008

Question

0.00/5 (No votes)

See more:

Hello Friends !!

How to create setup file in vb.net 2008 as front end and sql server 2000 as back end.
How to create setup file which if install on one pc , then that setup file will not run on another pc. means one file install on one pc then that copy will not be install on other pc.

Is it require to install sql server on client pc.
with out installing sql server on client pc how should i use the in-built facility of sql.

Is it require to restore the database to client pc to run program on client pc.
or with out installing database , is it possible to run such program.

in short i want to know step by step procedure how to create a setup file in vb.net 2008 and want to create such setup file , which if i send to anyone through mail then he can easily install the copy.

I have created an desktop application with vb.net 2008 as front end and sql server 2000 as back end.

So please if anyone can help me in this solution.

Posted 11-Dec-11 23:16pm

mrustechnology

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2011-12-11T23:20:00

You should not include SQL Server in your installation. There are a couple of reasons:
0) You can only distribute SQL Server Express for copyright reasons - not SQL Server full version.
1) They may already have SQL Server installed on the network. If so, then they will presumably want to use that version.
2) If they do have SQL server installed and you start proliferating SQL server Express instances, you are going to annoy the heck out of the database administrator...
3) A single site installation of SQl Server is a lot more likely to be backed up than a number of scattered version under user control.
4) Sql server is quite complex for a "normal" user to install and administer - it is not a good idea!
5) It will destroy the primary advantage of using Sql Server over SqlCE or SQLite - multiuser access. If everyone installs their own copy of SQL server, then you will have multiple copies of your database, each used by a single person. This will cause some confusion, and (depending on how you wrote the original database) may take some considerable effort to combine into a single instance when the problem is realized.

koolprasad2003 · Answer 2 · 2011-12-11T23:30:00

Solution 2

Dear developer
1. Do not install SQL on each client machine. Install SQLServer on any central machine call it as database server
access that SQL server using connection string.
2. Or as OriginalGriff said you can install SQL Server Express on each machine.
3. Step by step guide to create Setup project.[^]

Posted 11-Dec-11 23:30pm

koolprasad2003

Comments

mrustechnology 12-Dec-11 5:40am

but all my system are at different location. If i have many client with different location then what to install on client machine . and if client dont know how to restore database then what to do. In short i want to send my whole application to client in mail . so how he will install my setup file and how he will connect with my database.