windows application deployment problem

Question

0.00/5 (No votes)

See more:

Dear expert,
I am doing a windows application using visual studio 2012, C# 4.0 and sql server management 2012. I am on the verge of completing the project but I am not able to deploy the same on client machine??
I want to know step by step procedure about how to deploy on client machine...??
do I need to install sql server management in client system?? my client has windows vista?? so do need to take sql server management studio 2008???
please help bcoz I m not understanding how to go about it...

Posted 3-Apr-15 23:17pm

keyur tandel

Add a Solution

1 solution

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 · Accepted Answer · 2015-04-03T23:36: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.

If you application needs multiuser DB access then you need someone at the client end who knows how to work with SQL server (or you will end up with a lot of support calls which aren't your problem) - if it only needs single user access then you shouldn't use SQL server at all! SqLite, SQLCE, or even Access are better solutions.

Other than that, use VS to add a Setup and Deployment project to your app, and that will take care of the "donkey work" of installing everything your app needs to run. Be aware that Vista did not come with .NET 4 as standard, so you will need a proper installer to ensure it is installed before you app will run.