Why no drive object?

[dgk]

Having searched far and wide in the net classes, and then having
searched far and wide in this newsgroup, it is obvious that there is
no Drive object. We have io.directory objects and a GetLogicalDrive s
method, but no way to manipulate the drives returned by
GetLogicalDrive s except for Management objects. Logically, shouldn't a
drive object just be part of System.IO? I really don't want to use the
FSO stuff.

This is lots of work just to duplicate the functionality of a
drivebox. Well, I'm sure MS had a good reason do make it so indirect.
Does anyone know what that reason is?

[Armin Zingler]

"dgk" <so*********@ze ro-spam-hotmail.com> schrieb

Having searched far and wide in the net classes, and then having
searched far and wide in this newsgroup, it is obvious that there
is no Drive object. We have io.directory objects and a
GetLogicalDrive s method, but no way to manipulate the drives returned
by GetLogicalDrive s except for Management objects. Logically,
shouldn't a drive object just be part of System.IO? I really don't
want to use the FSO stuff.

This is lots of work just to duplicate the functionality of a
drivebox. Well, I'm sure MS had a good reason do make it so
indirect. Does anyone know what that reason is?

I think the question is not related to the VB.NET language. Please post to
one of the Framework groups (microsoft.publ ic.framework[.*]).
--
Armin

http://www.plig.net/nnq/nquote.html
http://www.netmeister.org/news/learn2quote.html

[Herfried K. Wagner [MVP]]

* dgk <so*********@ze ro-spam-hotmail.com> scripsit:

Having searched far and wide in the net classes, and then having
searched far and wide in this newsgroup, it is obvious that there is
no Drive object.

As Armin says, that's not the right place for the question.

In .NET 2.0, there will be a 'DriveInfo' class:

<http://longhorn.msdn.m icrosoft.com/lhsdk/ref/ns/system.io/c/driveinfo/driveinfo.aspx>

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[dgk]

On 27 Dec 2003 00:06:53 +0100, hi************* **@gmx.at (Herfried K.
Wagner [MVP]) wrote:

* dgk <so*********@ze ro-spam-hotmail.com> scripsit:

Having searched far and wide in the net classes, and then having
searched far and wide in this newsgroup, it is obvious that there is
no Drive object.

As Armin says, that's not the right place for the question.

In .NET 2.0, there will be a 'DriveInfo' class:

<http://longhorn.msdn.m icrosoft.com/lhsdk/ref/ns/system.io/c/driveinfo/driveinfo.aspx>

Ok. Looks like something they just didn't have time to finish.

[Herfried K. Wagner [MVP]]

* dgk <so************ ******@zero-spam-hotmail.com> scripsit:

Having searched far and wide in the net classes, and then having
searched far and wide in this newsgroup, it is obvious that there is
no Drive object.

As Armin says, that's not the right place for the question.

In .NET 2.0, there will be a 'DriveInfo' class:

<http://longhorn.msdn.m icrosoft.com/lhsdk/ref/ns/system.io/c/driveinfo/driveinfo.aspx>

Ok. Looks like something they just didn't have time to finish.

ACK. Have a look at the complete class tree, a lot of new classes will
be added which were missing since .NET 1.0.

;-)

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[dgk]

On 27 Dec 2003 13:34:58 +0100, hi************* **@gmx.at (Herfried K.
Wagner [MVP]) wrote:

* dgk <so************ ******@zero-spam-hotmail.com> scripsit:

Having searched far and wide in the net classes, and then having
searched far and wide in this newsgroup, it is obvious that there is
no Drive object.

As Armin says, that's not the right place for the question.

In .NET 2.0, there will be a 'DriveInfo' class:

<http://longhorn.msdn.m icrosoft.com/lhsdk/ref/ns/system.io/c/driveinfo/driveinfo.aspx>

Ok. Looks like something they just didn't have time to finish.

ACK. Have a look at the complete class tree, a lot of new classes will
be added which were missing since .NET 1.0.

;-)

Just one more thing then. The example in the MSDN library for
Freespace uses FSO and I don't want to. I swiped some of this code
from a previous post of yours and I just cannot figure out how to drop
the drive name or volume or any other property into a listbox. Can you
please tell me what I'm doing wrong? The 1 to Length-1 is intentional,
I'm skipping A: because I didn't want to start off with a removable
drive just in case that was a problem. As is, I'm getting an Invalid
Class error for each drive. I've tried a hundred permutations of this
code.

For i = 1 To Drives.Length - 1
DriveL = "Win32_LogicalD isc.DeviceID=" & Chr(34) &
Drives(i).Subst ring(0, 2) & Chr(34)
'DriveL = "Win32_LogicalD isc.DeviceID="" C:" & """"
Dim Mydisk As New System.manageme nt.ManagementOb ject(DriveL)
MessageBox.Show ("Testing " & Mydisk.Path.ToS tring) ' this is
just returning DriveL, which is a string. But no error.
Dim diskProperty As System.Manageme nt.PropertyData
Try
ListBox1.Items. Add(Mydisk.Prop erties("FreeSpa ce").ToString )
'For Each diskProperty In Mydisk.Properti es
' ListBox1.Items. Add(diskPropert y.Name)
' 'ListBox1.Items .Add(diskProper ty.Value)
'Next
' ListBox1.Items. Add(Mydisk.Prop erties("Name"))
Catch ex As System.Exceptio n
MsgBox("Error is " & ex.Message)
End Try
Next