Hi,

Can you tell me how to automatically include a new compile application
in Visual Basic into visual source safe. The only way I have figure
out how to do this so far is to include the executable in the list of
files. Launch VSS, check out the exe, compile it, then check it back
in again.

Not very productive if you ask me! I really want to keep track of the
executables, but I'm really hoping there is a simplier i.e. automated
way, to do this!

Let me know if you have a solution. 

Thanks.

Thierry

Our company uses source safe and we keep track of the executables in a
separate release folder from the source code. The reason for this is
because executables are binary files and unlike source code, source
safe cannot store only the changes made to them from one version to
the next. For executable the entire file is saved in source safe and
this quickly uses a lot of disk space.
If you were to automatically checkin the executable each time you
compile this could lead to a lot of wasted space if you were
developing and debugging the executable.

We tend to label the source code when we have reached a release build
and the executables are then checked into a separate folder that we
can use to go back to any version and get a particulare version out.
This is useful when multiple executables are updated for a given
change.

As far as you're original question I have not seen a way of checking
in the executable automatically.

Hope this helps.
Darren.

I would probe for the reasons to keep a binary file in SourceSafe.  At
a glance it might seem that SourceSafe is a "backup" manager, and
there is some truth to this.  But if one is really interested in
backup protection, one then has to realize the problem has simply
moved from backing up the working directories to backing up the
SourceSafe directories.

SourceSafe is a reasonably sophisticated tool for (source) version
management within the Visual Studio development environment (and of
course it can be used as a standalone client).  And in principle one
could have custom build rules to checkin the executable each time it
gets linked, but surely this cannot have the value that you might
hope.  A decision to preserve a build would most properly follow at
least a basic testing regimen.  Therefore I'd be much more enthused
about a test harness type automation rather than one for VSS.

regards, mathtalk-ga