We are running fully patched 6.0; but unfortunately I think I found the issue: http://www.developsense.com/testing/VSSDefects.html > "Automation API Issues". It appears that this is expected behavior for VSS; so I'll need to develop a workaround to handle searching to the additions and removals to incorporate those into our unit testing process. Surprisingly, I did some pretty intense searching before finding any resources that address this issue. Thank you both for your help,
Jen On Jun 4, 12:09 pm, "Phil Sayers" <[email protected]> wrote: > Make sure your VSS is fully patched. > > What vss version are you running? 6.0? 2005? > > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > > Behalf Of Jen B. > Sent: Thursday, June 04, 2009 11:20 AM > To: ccnet-user > Subject: [ccnet-user] Re: Modification History Issue with VSS > > 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 -- Hide quoted text - > > - Show quoted text -
