Title: Message
Hi
Russell,
Whilst
I can see what you are saying, I don't really think this is NAnt's fault.
Really, you shouldn't have anything in your current view of your archive that
isn't part of the current solution.. The problem is that VSS doesn't version
folders. You could switc
851&aid=1149608&gro
up_id=54790
**
Thanks
Shelly
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Wilson,
Glenn
Sent: Friday, September 16, 2005 9:43 PM
To: 'nant-users@lists.sourceforge.net'
Subject: RE: [N
Hi,
I think the solution to this problem is more to do with the way you manage
your source control processes rather than a technical one. We use labels
within our PVCS repository to label all files associated with a particular
release . Thus, a solution file with a label of say
MyAPP_ReleaseDate
g, Russell
E.; nant-users@lists.sourceforge.net
Subject: RE: [Nant-users] Solution
task and VSSGET
If
it is in a separate folder in VSS you can open properties and mark it as a
hidden folder (for the user that your script fetches as). The better
solution is to just delete it though.
---
Behalf Of Baker,
SteveSent: Friday, September 16, 2005 4:32 PMTo: Hogg,
Russell E.; nant-users@lists.sourceforge.netSubject: RE:
[Nant-users] Solution task and VSSGET
Pretty sure nothing
like that exists right now.
Typically SCM purists
would say if you have removed
Title: Message
Pretty sure nothing like that exists right
now.
Typically SCM purists would say if you
have removed something from the solution you should also delete it from VSS. You
can still view it in the history and all that fine jazz.
But back to reality, if you ever do create