Ron -
Draco.net pulls out the latest files for a build, it does not get at a
particular label point. It builds when it has detected changes since the
latest build or Draco.net can be "forced" to run a build through the
dracocli.exe tool.
NAnt could be used to get files from source control at a la
After letting it run for some time, this is the result that I have gotten. Note
though that I do have vs.net 2003 installed and functioning on the machine
without any problems.
4/6/2004 4:38:11 PM - Simulator : Checking module for changes
4/6/2004 4:38:11 PM - Detected path: C:\Program Files\Micro
Abdullah -
Each time Draco.net is started, initially it looks for changes since the
start of the service.
Here are some things to try that might help.
1) Try starting the service and waiting a minute, then making a change to
once of the files in source control under the $/Simulator path somewhere
Running locally, same result. Though it does not say code 100. What else should
I try?
4/6/2004 3:48:34 PM - Starting Draco.NET
4/6/2004 3:49:34 PM - Simulator : Checking module for changes
4/6/2004 3:49:34 PM - Detected path: C:\Program Files\Microsoft Visual
Studio\Common\VSS\win32
4/6/2004 3:49
Abdullah Siddiqui <[EMAIL PROTECTED]> wrote:
> the identity that the service is running under is my account.
>
>
Abdullah,
The problem we all have with VSS, is that Microsoft, in their ultimate wisdom, return
error code 100 for a number of problems it might experience
during an invokation. T
