Is there a way to enable saving Alternate Named Data Streams in Vault?
It seems they are getting stripped/ignored on file loading/importing.
We'd like to transition to ADS and simplify our existing cryptic naming convention. Source code headers are an alternative, but they don't work on binary files.
NTFS ADS Support?
Moderator: SourceGear
I'm not an expert on ADS, but the .NET libraries don't appear to have any classes or functions designed to deal with them. Vault uses the .NET file stream classes for all its file I/O, and I can't find any mention of methods to enumerate or read from ADS. Also, Vault's repository structure wasn't designed to contain alternate streams, so we'd have to design some storage mechanism (perhaps just allow the colon character to be stored and hide the alternate files in the Vault client).
I can also see some problems in environments where some users work on NTFS, some on FAT32, and some on Unix filesystems. When the FAT32 user checks in a new version of a file that used to have alternate streams, are they removed from the repository?
Sorry, but I don't think this will make a near future version of Vault.
I can also see some problems in environments where some users work on NTFS, some on FAT32, and some on Unix filesystems. When the FAT32 user checks in a new version of a file that used to have alternate streams, are they removed from the repository?
Sorry, but I don't think this will make a near future version of Vault.
Shaw Terwilliger
SourceGear LLC
`echo sterwill5sourcegear6com | tr 56 @.`
SourceGear LLC
`echo sterwill5sourcegear6com | tr 56 @.`