Comments by emcp - CodeProject

emcp 10-May-14 12:45pm View

try putting the OpenFileDialog in a try catch block.

emcp 10-May-14 12:36pm View

try Message.ShowDialog("");

emcp 10-May-14 12:34pm View

Deleted

Instanciating a new dialog will rule out any event you may have added to the dialog. Then it looks like its triggered by the filesystem or display.

emcp 10-May-14 12:28pm View

You tried reinstanciating, as I said 2 comments back?
Yes .Net is managed, however you can use unmanaged blocks, dllimports, COM, DirectX...

emcp 10-May-14 11:09am View

You shouldn't be getting this type of exception in managed memory.
So if that didn't work - then are you using any unmanaged objects that are being triggered (as OriginalGriff is indicating).

emcp 10-May-14 10:52am View

try reinstanciate your dialog:
OpenFileDialog dlgOpen = new OpenFileDialog();
DialogResult dr = dlgOpen.ShowDialog();

emcp 10-May-14 10:06am View

OpenFileDialog is a built in class, and calling ShowDialog is throwing a memory exception. So making a new project and adding an OpenFileDialog, and calling ShowDialog, will rule out that anything is corrupted.

Otherwise, ensure you are not using a custom OpenFileDialog class.

Then check that the default folder, properties etc.. are not assigned to something that could throw an exception. However that would seem unlikely.

emcp 10-May-14 9:39am View

Does OpenFileDialog class work in an empty new project?

emcp 10-May-14 9:35am View

Have you marked the client project as startup: Right-click and "Set as startup Project"?

emcp 10-May-14 9:12am View

And the types of Minimum and Maximum?

Comments by emcp (Top 10 by date)