How to create a MSI Package combining the VS 2005 project setup and the installation scripts of SQL Server 2008 into one single package and deploy it to Dev?

Question

0.00/5 (No votes)

See more:

VS2005

I have 3 projects in my VS 2005 single solution (1 Web Project, 2 other C# projects). I create the setup for deploying the website using Setup Project Templates available in Setup and Deployment category. Now I have .sql file needed for the website. Currently I need to run this setup to install the website firstly. Secondly I need to execute scripts that is the .sql file in the MS SQL Server 2008 where the website DB is already available. My requirement now is to give this .sql file and website as a single setup package? Is there any possibility of bundling this package and the SQL scripts into a MSI package? Can some one please help me in this regard.

Posted 6-Mar-13 16:54pm

Vandana M J

Add a Solution

Comments

Sergey Alexandrovich Kryukov 6-Mar-13 23:36pm

Very brief advice: Don't get into it. Why? I would highly recommend to require the user to use their version of SQL Server, based on your user's license. Make is a prerequisite for your product.
—SA

Vandana M J 7-Mar-13 0:11am

Hi Sergey,

I dont find your answer relevant to my question.
I actually have .sql scripts and my .net code is dependent on these queries to make the website work.
When this is the case, my requirement is I need to install website and these sql scripts by single click on Setup i.e bundling code setup and .sql scripts as single MSI package?

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)