VS2005 DialogResult

rk · Feb 28, 2006

According to the docs, I would expect to check the result of an
OpenFileDialog in a VS 2005 CLR Windows Forms application this way:

if (openFileDialog1->ShowDialog()==
DialogResult::OK)

However, this does not work, and I have to use:

if (openFileDialog1->ShowDialog()==
System::Windows::Forms:

ialogResult::OK)

Did I miss anything, or is this a bug?

Thanks
Richard

Jochen Kalmbach [MVP] · Feb 28, 2006

Hi rk!

According to the docs, I would expect to check the result of an
OpenFileDialog in a VS 2005 CLR Windows Forms application this way:

if (openFileDialog1->ShowDialog()==
DialogResult::OK)

However, this does not work, and I have to use:

if (openFileDialog1->ShowDialog()==
System::Windows::Forms:ialogResult::OK)

Did I miss anything, or is this a bug?

The short-version only works, if you have added

using System::Windows::Forms;

at the top (or at least before you use the above code).
Or did I miss something in your post?

--
Greetings
Jochen

My blog about Win32 and .NET
http://blog.kalmbachnet.de/

Carl Daniel [VC++ MVP] · Feb 28, 2006

Jochen Kalmbach said:
Hi rk!

The short-version only works, if you have added

using System::Windows::Forms;

using namespace System::Windows::Forms;

that is...

-cd

rk · Feb 28, 2006

Hi Jochen,

I had added

using namespace System::Windows::Forms;

but this did not prevent the problem. I know, that

if (openFileDialog1->ShowDialog()==
System::Windows::Forms:

ialogResult::OK)

and

using namespace System::Windows::Forms;
if (openFileDialog1->ShowDialog()==DialogResult::OK)

should be equivalent. So I would expect it to be a bug if they are not.

Or not?

Richard

Jochen Kalmbach [MVP] · Feb 28, 2006

Hi rk!

using namespace System::Windows::Forms;

but this did not prevent the problem. I know, that

if (openFileDialog1->ShowDialog()==
System::Windows::Forms:ialogResult::OK)

and

using namespace System::Windows::Forms;
if (openFileDialog1->ShowDialog()==DialogResult::OK)

should be equivalent. So I would expect it to be a bug if they are not.

What prolems do you get???
For me it works without any problems in VS2003 and VS2005...

--
Greetings
Jochen

My blog about Win32 and .NET
http://blog.kalmbachnet.de/

R.Kaiser · Feb 28, 2006

Hi Jochen,

strange. When compiling

private: System::Void openToolStripMenuItem_Click(System::Object^
sender, System::EventArgs^ e) {

if (openFileDialog1->ShowDialog()== DialogResult::OK)
//System::Windows::Forms:

ialogResult::OK) // this works
{
richTextBox1->LoadFile(openFileDialog1->FileName);
}
}

I get

1>c:\vs2005\projekt1\projekt1\Form1.h(156) : error C2039: 'OK': Ist
kein Element von 'System::Windows::Forms::Form:

ialogResult'
1> c:\vs2005\projekt1\projekt1\Form1.h(23): Siehe Deklaration
von 'System::Windows::Forms::Form:

ialogResult'
1>c:\vs2005\projekt1\projekt1\Form1.h(156) : error C2065: 'OK':
nichtdeklarierter Bezeichner
1>Das Buildprotokoll wurde unter
"file://c:\VS2005\Projekt1\Projekt1\Debug\BuildLog.htm" gespeichert.
1>Projekt1 - 2 Fehler, 0 Warnung(en)

If this works for you - what could I have done wrong?

I am using

Microsoft Visual Studio 2005
Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727
Installierte Edition: Professional

Thanks
Richard

Jochen Kalmbach [MVP] · Feb 28, 2006

Hallo R!

private: System::Void openToolStripMenuItem_Click(System::Object^
sender, System::EventArgs^ e) {

if (openFileDialog1->ShowDialog()== DialogResult::OK)
{
richTextBox1->LoadFile(openFileDialog1->FileName);
}
}

I get

1>c:\vs2005\projekt1\projekt1\Form1.h(156) : error C2039: 'OK': Ist
kein Element von 'System::Windows::Forms::Form:ialogResult'
1> c:\vs2005\projekt1\projekt1\Form1.h(23): Siehe Deklaration
von 'System::Windows::Forms::Form:ialogResult'

Ok! Now I see the problem!
You are using this inside a Form-derived class...
The Form itself contains a member called "DialogResult".
The compiler is using this member instead of the enum...

Also if you enter "::" after "DialogResult" you get the "correct" hint
(you have only "get" or "set" and no values of the enum!).

AFAIK the shortest version is:
Windows::Forms:

ialogResult::OK

Inside a Form...

By the way: Es gibt auch eine deutschsprachige newsgroup für managed C++
/ C++/CLI:
microsoft.public.de.german.entwickler.dotnet.vc

--
Greetings
Jochen

My blog about Win32 and .NET
http://blog.kalmbachnet.de/

R.Kaiser · Feb 28, 2006

Jochen said:
Hallo R!

Ok! Now I see the problem!
You are using this inside a Form-derived class...
The Form itself contains a member called "DialogResult".

Thanks, that would be an explanation.

But where does this member come from? I have not inserted it.

The compiler is using this member instead of the enum...

Also if you enter "::" after "DialogResult" you get the "correct" hint
(you have only "get" or "set" and no values of the enum!).

AFAIK the shortest version is:
Windows::Forms:ialogResult::OK

Inside a Form...

By the way: Es gibt auch eine deutschsprachige newsgroup für managed C++
/ C++/CLI:
microsoft.public.de.german.entwickler.dotnet.vc

Vielen Dank

Richard Kaiser

Jochen Kalmbach [MVP] · Feb 28, 2006

Hallo R!

Thanks, that would be an explanation.

But where does this member come from? I have not inserted it.

It is a member of the "Form"-class:
http://msdn2.microsoft.com/en-us/library/system.windows.forms.form.dialogresult.aspx

Also in the example they use
:

ialogResult::OK
as a shortcut... but it does not compile...

Maybe there is a shorted way; but I do not know it currently...

--
Greetings
Jochen

My blog about Win32 and .NET
http://blog.kalmbachnet.de/

R.Kaiser · Feb 28, 2006

Jochen said:
Hallo R!

It is a member of the "Form"-class:
http://msdn2.microsoft.com/en-us/library/system.windows.forms.form.dialogresult.aspx

Also in the example they use
:ialogResult::OK
as a shortcut... but it does not compile...

Maybe there is a shorted way; but I do not know it currently...

Vielen Dank
Richard Kaiser

Marcus Heege · Feb 28, 2006

Regarding the scope of identifiers, C++/CLI is very picky. You are probably
facing a problem related to this. Check if you have defined something (e. g.
a member of your class) "DialogResult". This can easily cause such a
problem.

Here is another example:

#using "System.Drawing.dll"
using namespace System:

rawing;
ref struct X
{
property Size Size
{
// the line below fails even though the namespace System:

rawing is
opened
Size get() // type name Size conficts with property name Size
{
return Size();
}
// workaround
// System:

rawing::Size get() // type name Size conficts with property
name Size
// {
// return System:

rawing::Size();
// }
}
};

Marcus Heege

This code is untested. Please test it

Jochen Kalmbach [MVP] · Mar 1, 2006

Hi Marcus!

Regarding the scope of identifiers, C++/CLI is very picky. You are probably
facing a problem related to this. Check if you have defined something (e. g.
a member of your class) "DialogResult". This can easily cause such a
problem.

Have you a pointer to the docu???
Because the same code works perfectly in VS2003...

By the way: The member "DialgResult" is defined in
"System::Windows::Forms::Form"... so the problem occurs in *every*
Form-derived class.

--
Greetings
Jochen

My blog about Win32 and .NET
http://blog.kalmbachnet.de/

an OpenFileDialog problem	2	May 26, 2005
wpf version of OpenFileDialog	0	Aug 18, 2010
VC++ Express, Strings and files - CONFUSED	2	Nov 20, 2007
Dialog Threading error	2	Jan 17, 2006
When is it good to use the DialogResult for a Button	1	Sep 1, 2010
Can someone please check my understanding here and suggest fix	4	Nov 23, 2006
openfiledialog in silverlight	1	May 6, 2009
OpenFileDialog.RestoreDirectory no longer works in Vista afterinstalling VS 2008	2	Dec 19, 2007

VS2005 DialogResult

rk

Jochen Kalmbach [MVP]

Carl Daniel [VC++ MVP]

rk

Jochen Kalmbach [MVP]

R.Kaiser

Jochen Kalmbach [MVP]

R.Kaiser

Jochen Kalmbach [MVP]

R.Kaiser

Marcus Heege

Jochen Kalmbach [MVP]

Ask a Question

Similar Threads