That's exactly what I was afraid of. Maybe I can get into the code to see the command line CC is using to query VSS for modifications to see if I can replicate the error outside of Cruise Control; and then see if there are any VSS workarounds available to circumvent the problem. Thanks for your help!
Jen On Jun 3, 5:18 pm, Craig Sutherland <[email protected]> wrote: > Hi Jen, > > I've had a quick look at the code. It appears that all CC.NET does is > split the path name provided by VSS into folder and file names. > > This means the problem is VSS is not returning the full path and > unfortunately I don't think we can do much about that. > > Maybe one of the devs with VSS can take a look at this (I use SVN so I > can't debug it for you). > > Craig > > On Jun 4, 6:22 am, "Jen B." <[email protected]> wrote: > > > > > I'm using the ModificationWriter task to collect a list of changes > > from Visual SourceSafe to use for unit testing / validation. This > > process works great if the modification type is "Checked In"; however, > > when the modification is an addition or deletion, the "FolderName" > > information doesn't include the full path to the file. This is > > problematic because of the massive number of files we are managing; > > there is no way to identify where the file lives in the directory > > structure without the explicit path. Does anyone have any ideas to > > workaround this problem? Thanks! > > > Jen- Hide quoted text - > > - Show quoted text -
