Click here to Skip to main content
13,046,356 members (112,775 online)
Rate this:
Please Sign up or sign in to vote.
See more:
I am trying to deploy a beta of my first project and was wondering if anyone had any suggestions of how to include a separate folder of files in the deployment (they are to be stored on the C:\ drive once the install is completed, outside of the installation directory). Do I add them in the reference paths area of the properties wizard prior to publishing? I'm new to deployment of projects. I'm currently using Visual Studio 2012.

Also, how can I deploy a SQL Server Compact database? When I try to install a deployment on another computer, it tells me that the path to the database is invalid. It's still referencing the path name in the project.
Posted 8-Oct-12 5:54am
Updated 8-Oct-12 7:58am
To start with, you should not even assume C: exists on the target computer of your customer -- it really may not exist. All deployment is done to the directory supplied by the user, with a possibility of using some defaults, of course.

1 solution

Rate this: bad
Please Sign up or sign in to vote.

Solution 1

You can add any files to the installation, even if they are not in your project used to build the software. You can add such directory and files when you create a deployment project. For example, if you create a deployment project from the project template "Setup and Deployment" which comes with Visual Studio, you will immediately see such possibility in the project tree (as a part of Solution Explorer) and its context menus.

I think the most recommended way of deploying of the SQL Server is making it a prerequisite for your product. This can resolve all possible licensing issues and the cases when a user already has the same or compatible server installed, so it gives more convenience and flexibility to your user as well.

joshrduncan2012 8-Oct-12 15:18pm
Thanks! What is the suggestion as to how to dynamically assign the connection string instead of hardcoding the path name to the database? That's what is preventing me from successfully installing the deployment.
Basically, it should be prescribed in a configuration file. The setup project can present some default; and the user should be able to manually override it, even after the setup.

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

  Print Answers RSS
Top Experts
Last 24hrsThis month

Advertise | Privacy | Mobile
Web01 | 2.8.170713.1 | Last Updated 8 Oct 2012
Copyright © CodeProject, 1999-2017
All Rights Reserved. Terms of Service
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100