Print problem in VB.net

Question

0.00/5 (No votes)

See more:

I have a code to print in VB.net. I don't have any problem with the printing as it works, but there is a part which is underlined by green, a warning on "DialogResult = OK".

Why the DialogResult = OK is underlined by green colour? The printing work only this underline is making me puzzled

The warning is: Access of shared member, constant member, enum member or nested type through an instance; qualifying expression will not be evaluated.

Posted 26-Apr-11 22:57pm

555336

Updated 26-Apr-11 23:25pm

v5

Add a Solution

2 solutions

Solution 1

Rebuild your app: it should go away.
If it doesn't then look at the error list pane: you should have a message that refers to it under "Warnings"

Posted 26-Apr-11 23:10pm

OriginalGriff

Comments

555336 27-Apr-11 5:12am

Read the warning it is giving me in the question below.

OriginalGriff 27-Apr-11 5:22am

Wayne is correct - it is a qualification problem: The compiler cannot tell if you mean "System.Windows.Forms.DialogResult" or "Me.DialogResult".
Never seen it complain like that before though...

555336 27-Apr-11 5:27am

Yes I included it and the warning disappeared. thank you.

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Wayne Gaylard · Accepted Answer · 2011-04-26T23:17:00

Solution 2

Try using the Fully Qualified Name ie

System.Windows.Forms.DialogResult.OK as your Form also has a DialogResult property

This should help

Posted 26-Apr-11 23:17pm

Wayne Gaylard

Updated 26-Apr-11 23:18pm

v2

Comments

OriginalGriff 27-Apr-11 5:23am

Well spotted! :thumbsup: and 5

Wayne Gaylard 27-Apr-11 5:27am

Ta!