OK to use FolderBrowserDialog ?

[Kevin R]

Hi All.
Reading the help file for FileBrowserDialog class, It says
in red letters at the top of the page

Note: This namespace, class, or member is supported only in version
1.1 of the .NET Framework.

Does this mean it is not supported in versions prior to V1.1, or does
it mean that it will not be supported in versions following V1.1 ?
or both

Should I be using something else instead ?

Just wondered.

Kevin R.

 

[Herfried K. Wagner [MVP]]

Reading the help file for FileBrowserDialog class, It says
in red letters at the top of the page

I assume you are referring to the 'FolderBrowserDialog' class.

Note: This namespace, class, or member is supported only in version
1.1 of the .NET Framework.

Does this mean it is not supported in versions prior to V1.1, or does
it mean that it will not be supported in versions following V1.1 ?
or both

It means that the class is not supported in .NET 1.0, even with Service
Packs applied.

Should I be using something else instead ?

If SP1 for .NET 1.1 is installed, it's safe to use this class. The original
implementation in .NET 1.1 suffered from a terrible buffer overflow problem.

 

[Kevin R]

Thanks for clearing that up for me.

It sounds as if I would have to verify that the user
has SP1 installed

Kevin R.

 

[Herfried K. Wagner [MVP]]

Thanks for clearing that up for me.

The bug I am talking about only occurs when dealing with long paths. Its
documentation can be found here:

FIX: Unexpected behavior occurs when a user selects a folder that has a long
path in a Folder dialog box in a .NET Framework 1.1 Windows Forms
application
<URL:http://support.microsoft.com/?kbid=830920>

 

[Kevin R]

The bug I am talking about only occurs when dealing with long paths. Its
documentation can be found here:

FIX: Unexpected behavior occurs when a user selects a folder that has a long
path in a Folder dialog box in a .NET Framework 1.1 Windows Forms
application
<URL:http://support.microsoft.com/?kbid=830920>

Ah, I see.
I think that rather than trying to establish whether the user has at
least version 1.1 sp2 and making that future proof, it might be easier
to just document it as a limitation.

Thanks,

Kevin R