VSS and compiled files

I have VSS integrated with my source code files just fine.....but what about the COMPILED files?  Maybe this is a dumb question, but does one need to track versions of compiled files as well as source code?

I would guess "no" because you can always generate the compiled files from the source code, right?

I think where my question is going is SHADOWING in VSS...where you can specify where (what directory) you want files to go to when they are compiled.

Just wondering.

Tom
LVL 5
Tom KnowltonWeb developerAsked:
Who is Participating?
 
millsoftConnect With a Mentor Commented:
Hi knowlton,

Our practice is to keep a separate VSS database of MASTER files whenever we ship a product.  This master contains the as-built binaries.  We do not keep the binaries in VSS except at these significant check-points because the files tend to be too large and bulky for VSS.

I suggest you use the XCopy technique for creating shadows of the binaries for testing/QA use, rather than using VSS.

Cheers!
Brad
0
 
davidastleConnect With a Mentor Commented:
At work, my VSS is set up to automatically copy all the output of every file to a specific directory.  I think this is exactly what you want... you can do it with macros in the post build event.  Unfortunately, i don't go back to work till monday, so if you are patient, i can tell you then.
0
 
davidastleCommented:
oops.. my mistake. ignore my comment.
0
 
Tom KnowltonWeb developerAuthor Commented:
I am satisfied with what I have heard so far.

I think I will just use xcopy.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.