|
Well the thing I find most odd is that when I use the command line it fails every other run. The windows app version proceeds without a hitch, not one failing build.
The reason we are keeping those files checked out is because we have a problem with individuals "forgetting" to check the assembly files back in. We basically dont want them to check them out in the first place. Since SourceSafe doesnt allow file level permissions, this was our work around.
SourceSafe is throwing errors when this fails. It is basically throwing an error because files are checked out and it cannot check for itself. But if you look at the successful builds, it is not giving that error and it proceeds on. I guess my question now is what is the expected behavior?
|