How do I rebuild a project from scratch?

[billsinclaol_com]

We don't seem to have an easy to rebuild a project from JUST the source code.

Assume I have all the source code files in a folder:

I can't start a new project in that same folder I had before.
It does not let me name the project the same as before, so I have to
make a new and different project name and start it in another folder.

So then the source files are in a different place than the project,
which is rather awkward.

Why can't I put the project BACK where it was before?

BTW, can we have a utility that lets us pick the source files
stating with ONE main program file? So it would go thru
and pick them out based upon unsatisfied externals.

[anthonyrichards]

Why do you want to do this?
You can delete files from a project but the files remain.
You could delete all the files from a project leaving an empty project and just its settings.
You can then add files back into a project, giving you a changed project but with the same name and settings.
You would be wise to copy the project files to a backup place before doing this as you could then recover from mistakes you might make.
You do not need to delete a project in order to change it.

You use the term 'build'. A project is 'created', a solution is 'built'.

You 'build' a solution for a project by compiling all the files included within it and then linking the object files and linking any default and named libraries mentioned in the project properties.

[jimdempseyatthecove]

Anthony, the problem is real.

Assume for the sake of argument:

a) You download an archive containing something of interest. (say GLUT library source)
b) The archive is labled GLUT.1.2.3.4.zip
c) You unzip to GLUT.1.2.3.4 into your favorite utilities folder myUtils\GLUT.1.2.3.4
d) GLUT came off a Linux machine and you have no Visual Studio Solution and/or Projects
(or the ones that came with the archive were from the next version of VS which you do not have yet)
e) You try to make a solution GLUT.1.2.3.4. however VS won't let you do that.
f) your rename GLUT.1.2.3.4 to BARF
g) You created GLUT.1.2.3.4 Solution (empty)
h) You copy BARF files to GLUT.1.2.3.4 (or play a rename game and copy the empty solution back)
i) you now populate the project(s) in the solution.

VS (IMHO) should examine the folder for an existing solution of the name (of the folder). Only if the solution exists should VS balk at creating a new solution over the top of and existing solution. It would be acceptible for VS to warn "Folder of same name ('GLUT.1.2.3.4') exists. Continue?" steps e,f,g,h are useless hoop jumping exercizes (when solution/project not present in folder).

Also, assume due to update or for whatever reason you decide to nuke the project and solution files (but keep the sources). You cannot create a new Solution/Project using the same name (without doing the e,f,g,h hoop jump).

There is no reason for this sillyness (but this is a MS issue not Intel issue)

Jim Dempsey

[WSinc]

Dempsey hit the nail right on the head.

Sometimes it IS necessary to scrap a project and start over.

Also, I would like to be able to put nore than one project in the same parent folder,
sharing some of the source code, and binaries. includes, etc.

When I do a "BUILD" my understanding is that I make a new execuatble from the
same set of source files in my project I have already set up.

So I don't understand Mr Richards' comment.