Move the whole project to another pc

Question

1.00/5 (1 vote)

See more:

SQL-Server-2008R2

, +

I've written a project in c# (database included) and I used entity framework 6
the last technology and now want to move the whole project to another pc.

what matters should I concern about? or tell me how can I manage that without error!
please explain clear ,I'm new
Tanx

Posted 11-Apr-15 7:31am

Nima.naqipoor

Updated 11-Apr-15 7:38am

v2

Add a Solution

Comments

Maciej Los 11-Apr-15 14:07pm

What kind of database?

Nima.naqipoor 11-Apr-15 14:27pm

Sql

Sascha Lefèvre 11-Apr-15 16:41pm

As long as you don't delete anything on the first PC you don't run any risk of losing anything, even if it doesn't work on the new PC on your first attempt. So just go ahead, try it and see if you run into a problem - maybe there won't be any :-)

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)

Sergey Alexandrovich Kryukov · Accepted Answer · 2015-04-11T13:36:00

There are no concerns at all, except just one: your code itself. Simply copy all source code from one computer to any directory of another computer. You need to have all the build tools and all dependencies to be installed on that computer, including SQL server and all libraries you use. Now, look: if it does not work immediately, it means that you don't really have a working project, even if it was "working" on the first computer.

The similar thing should happen when you copy just to output directory. You won't need Visual Studio, but you would need a compatible .NET version on the target computer, and all dependencies installed. Everything should work right away. If not — see above.

I would start with one simple and wise principle here: consider troubles in the order they appear. With some experience, you will develop the ability to predict them and eliminate them before they appear.

—SA