Visual Studio 2003 Deployment

Project / Copy Project

Do not use FPS rather use the UI to XCOPY to a local (pre-made) site, only files needed for this project.

NOTE: ANY ERROR IS FATAL TO THE DEPLOYMENT OF THE APPLICATION BUT IT WILL NOT ROLLBACK, IT WILL PARTIALLY DEPLOY. ALWAYS DEPLOY TO A STAGE DIRECTORY (and, of course, test this stage deployed version first) (LOCAL TO TARGET) AND THEN XCOPY OVER.

I discovered this three ways (perhaps because I can be particularly obtuse @ times ...)

1.) Code I rolled did not do what it should ... (Gee, duh ... (and yes, I was staging it))

2.) Funny thing how the VS deployment tool would finish so quickly after encountering an error (i.e. it took 30 seconds when an XCOPY took 2 minutes or more ...)

3.) Hmmm ... My local solution has a rather complex file hierarchy but ... I only see first level hierarchy (and for the immediate sub-levels there are no contents) ... Not sure about the priority/pattern of XCOPY (about which I am guessing the VS 2003 IDE is trying to obfuscate) but ... isn't it funny that if "img21.jpg" & "img22.jpg" (of a second level directory) are there but it bombs (modal) on "img23.jpg" (which it turns out is missing in source but is in VSS manifest) and then "img24.jpg" is not in the subdirectory of the deployed/stage solution (after one hits "OK" on the modal) (but it is in the source directory ...)

Point: Not sure about the exact order of a VS "Copy Project" deployment but if there is an error it is fatal, does not rollback and can leave you with a partial/mixed deployment if you don't stage (use good practices).