Error when using FolderBrowserDialog

[Aniruddha Pai]

Hi,

I use a folderbrowserdialog in my application.
When I try to invoke the FolderBrowser for the first time,
I get an error "The procedure entry point
RtlUnhandledExceptionFiler could not be located in the
dynamic link library ntdll.dll "The application works fine
after that.
This has started appearing after I shifted to VS.net 2003.
I was using a wrapped version of the FolderBrowser class (
Since there was no inbuilt Folder Browser dialog) in
VS.net 2002 and it worked fine.
But ever since I have shifted to VS.Net 2003, I have
started getting this error. Has anybody ever faced this
problem before?

Thanks
Aniruddha Pai

 

[Herfried K. Wagner [MVP]]

I use a folderbrowserdialog in my application.
When I try to invoke the FolderBrowser for the first time,
I get an error "The procedure entry point
RtlUnhandledExceptionFiler could not be located in the
dynamic link library ntdll.dll "The application works fine
after that.
This has started appearing after I shifted to VS.net 2003.
I was using a wrapped version of the FolderBrowser class (
Since there was no inbuilt Folder Browser dialog) in
VS.net 2002 and it worked fine.
But ever since I have shifted to VS.Net 2003, I have
started getting this error. Has anybody ever faced this
problem before?

A new bug in the FolderBrowserDialog? This dialog seems to be _very_
buggy, there are now at least 3 really ugly bugs with this class. I
would continue using the pinvoke replacement.

 

[Aniruddha Pai]

I am getting the same error even with the wrapped version
of the Folder Browser class!!
What is the pinvoke replacement?

 

[Herfried K. Wagner [MVP]]

I am getting the same error even with the wrapped version
of the Folder Browser class!!
What is the pinvoke replacement?

Sorry, the pinvoke replacement is the wrapped version... I don't have
any idea why the error occurs.

 

[Joe White]

Do you have an [STAThread] attribute on your application's Main() method?
If not, try adding one.

 

[Serg Novogilov]

Also you do not request any additonal feature,
try to install Dialog Workshop .NET.
There is pinvoke-based wrapper for SHBrowseForFolder
and we never had any bug reports about it.
Try to use this component as indicator whether this problem in
your sources or OS installation.

Visit this page to download:
http://www.componentage.com/download.htm


Serg
COMPONENTAGE Software
http://www.componentage.com