<div>
oops.. my mistake. ignore my comment.
</div>


<div>
I am satisfied with what I have heard so far.<br />
<br />
I think I will just use xcopy.
</div>


I am satisfied with what I have heard so far.

I think I will just use xcopy.

<div>
<div class="content wysiwyg-content">
I have VSS integrated with my source code files just fine.....but what about the COMPILED files? &nbsp;Maybe this is a dumb question, but does one need to track versions of compiled files as well as source code?<br />
<br />
I would guess &quot;no&quot; because you can always generate the compiled files from the source code, right?<br />
<br />
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.<br />
<br />
Just wondering.<br />
<br />
Tom
</div>
</div>


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

VSS and compiled files

C# is an object-oriented programming language created in conjunction with Microsoft’s .NET framework. Compilation is usually done into the Microsoft Intermediate Language (MSIL), which is then JIT-compiled to native code (and cached) during execution in the Common Language Runtime (CLR).