Actually, the drive is a physical volume. It's a partition on my hard
drive. I really find it weird that the .NET framework even lists this
apparently special directory at all! I checked on the C: drive and it
appears to have one too! Again, I can't see it if I use explorer or dir.
It's just strange.

One of the workarounds I can think of is the following:

<?xml version="1.0" encoding="utf-8" ?>
<project name="example" default="clean">
    <target name="clean">
        <foreach item="Folder" in="T:\" property="folder">
            <delete unless="${folder == 'T:\System Volume
Information'}">
                <fileset basedir="${folder}">
                    <include name="**\bin" />
                    <include name="**\obj" />
                </fileset>
            </delete>
        </foreach>
    </target>
</project>

It's a little ugly, but it gets the job done.

> -----Original Message-----
> From: Felice Vittoria [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 11, 2004 2:12 PM
> To: Castro, Edwin Gabriel (Firing Systems Engr.); nant-
> [EMAIL PROTECTED]
> Subject: RE: [Nant-users] Can't access "System Volume Information"
when a
> drive root is specified as basedir of a fileset
> 
> Edwin,
> 
> I faced a similar situation not long ago.   What I ended up doing was
> running the script on the box itself and not using a mapped/UNC drive.
> 
> Felice
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Castro,
> Edwin Gabriel (Firing Systems Engr.)
> Sent: Thursday, November 11, 2004 3:58 PM
> To: [EMAIL PROTECTED]
> Subject: [Nant-users] Can't access "System Volume Information" when a
> drive root is specified as basedir of a fileset
> 
> 
> Please observe the following output:
> 
> [output]
> T:\>type default.build
> <?xml version="1.0" encoding="utf-8" ?>
> <project name="example" default="clean">
>         <target name="clean">
>                 <delete>
>                         <fileset basedir="T:\">
>                                 <include name="**\bin" />
>                                 <include name="**\obj" />
>                         </fileset>
>                 </delete>
>         </target>
> </project>
> 
> T:\>nant -f:default.build
> NAnt 0.85 (Build 0.85.1766.0; nightly; 11/1/2004)
> Copyright (C) 2001-2004 Gerry Shaw
> http://nant.sourceforge.net
> 
> Buildfile: file:///T:/default.build
> Target(s) specified: clean
> 
> 
> clean:
> 
> 
> BUILD FAILED
> 
> T:\default.build(5,5):
> Error creating FileSet.
>     Access to the path "T:\System Volume Information" is denied.
> 
> Total time: 0.4 seconds.
> 
> 
> T:\>cacls "T:\System Volume Information"
> T:\System Volume Information NT AUTHORITY\SYSTEM:(OI)(CI)F
> 
> 
> T:\>
> [/output]
> 
> The volume mounted on drive T: has an NTFS filesystem. It's quite
> obvious that the problem is lack of permissions. I wonder why NAnt can
> see this "special" directory. I say "special" because I can't see it
in
> explorer or on the command line using dir. I can think of a few
> workarounds for this problem but I think it may be better solved in
the
> NAnt code for the long run. What happens when someone else wants to do
> something similar and they encounter this condition?
> 
> --Edwin
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_idU88&alloc_id065&op=ick
> _______________________________________________
> Nant-users mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/nant-users


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id065&op=click
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users

Reply via email to