Issues compiling with projects saved to a different folder

Question

1.00/5 (1 vote)

See more:

I'd been struggling the past couple of days trying to figure out why my program wouldn't run correctly when I executed the program direct from the Bin directory, but worked fine while with debug mode in VS2010.

I decided to go back to the original project folder I'd written it from and added the new bits of code into that and now it works?

I wanted to be able to have different folders for each version of the build, but it doesn't seem to like doing this? Could anyone explain why?

And also, if I am unable to copy and paste the original source files into a new directory, and work on a separate project, how can I keep new versions in separate directories?

Posted 21-Dec-15 12:33pm

Mendaharin

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)

Dave Kreskowiak · Accepted Answer · 2015-12-21T12:49:00

Why? Because you're not using a source control system, like Team Foundation Server, Subversion, Git, or whatever.

If you wanted to keep different versions of the source code and/or executable, you either have to copy those files off to a backup location somewhere or you have to use a version control system.

Garth J Lancaster · Accepted Answer · 2015-12-21T12:48:00

Im not exactely sure what you mean

usually, a debug exe will go to bin\debug while a release exe will go to bin\release - all this is customisable in the build settings for a project

>>

Quote:
And also, if I am unable to copy and paste the original source files into a new directory, and work on a separate project, how can I keep new versions in separate directories?

ok, what I would do is (depending on why Im doing this)

a) add a new project to my solution, and work on a copy of the files there - note that they are now completly separate from the original files, there's no going back - unless you do a manual process, for that you could use a 'difference' tool - I use 'Beyond Compare' from Scooter Software

OR

b) use source control, and 'branch' my changes, with a view that I might merge the code back into the mainline at some later stage

You havnt provided enough info on why you are doing this

Quote:
And also, if I am unable to copy and paste the original source files into a new directory, and work on a separate project, how can I keep new versions in separate directories?

so its a bit hard to advise you further (I'd be leaning towards source control personally... if you dont like command-line stuff, get a (free :-) ) copy of Atlassian SourceTree and use that)

Issues compiling with projects saved to a different folder

2 solutions

Solution 2

Solution 1

Add your solution here

Preview 0