Visual Basic

7-Feb-06 2:55

I have converted my first project to VS 2005 and I have 32 warnings that all say this:

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

I have variables setup as Friend Shared so I can use them throughout my project. Maybe I need to put these variables in a module to get away from this error?

Can someone give me a better explanation of what this error really means?

Confused? Confused | :confused:

Lost in the vast sea of .NET

-- modified at 8:56 Tuesday 7th February, 2006

Craster7-Feb-06 3:05

7-Feb-06 3:05

What it's effectively saying is that you no longer need to use an instance of many of the objects provided in the framework.

Eg:

Instead of using

Dim fFile as system.io.file
bVal = fFile.exists("c:\mytextfile.text")

you should instead use

bVal = system.io.file.exists("c:\mytextfile.text")

Basically you no longer need to create an instance to be able to use the functions that would normally be tied to that instance.

KreativeKai7-Feb-06 3:24

7-Feb-06 3:24

One line of code that I'm receiving this error is:

Dim diff As TimeSpan = start.op_Subtraction(System.DateTime.Now, start)

It worked fine in VS2003, but now I get this error. What do you suggest I change for this one?

Another line that is getting this warning is:

Me.cbxEEName.Cursor.Show

And finally another example is what I mentioned in my original message, I have a variable setup in one class (clsSqlCalls) as friend shared:

Friend Shared BeneficiaryDataset As DataSet

and I reference it in another class:

Dim clsSQL As New clsSQLCalls<br />
If clsSQL.BeneficiaryDataset.HasChanges Then

You answered this question. I replaced the code with:

If clsSQLCalls.BeneficiaryDataset.HasChanges Then

and it worked... Thanks.

Any suggestions on the first two examples of code?

Lost in the vast sea of .NET

Craster7-Feb-06 3:41

7-Feb-06 3:41

One thing to be clear about is that you are not getting error messages - you are getting warnings. Your code should compile and run (assuming it works elsewhere!) regardless of this, the compiler is just informing you about ways to improve the syntax of your code.

Can you let me know what 'start' is defined as, and also I assume that cnxEEName is a control on your form of some description?

KreativeKai7-Feb-06 5:14

7-Feb-06 5:14

Yes, you're right, they are warnings, and my code was working fine in 2003, but is working less than perfect in 2005. I'm tackling the warnings hoping the application will work the way it originally did.

Here is how start is defined:

Dim start As DateTime = System.DateTime.Now

Also cbxEEName is a combobox on one of the forms in this application.

I appreciate your feedback.

Lost in the vast sea of .NET

Craster7-Feb-06 5:31

7-Feb-06 5:31

You realise that the intellisense box will actually suggest what you need to replace these with to get rid of the warning? In this case:

dim start as DateTime<br />
dim diff as TimeSpan = system.DateTime.op_subtraction(system.DateTime.Now, start)

You still need the definition of start, as you are actually using the instance in the function, not just using it to gain access to the function.

For the second:

windows.forms.cursor.show()

I'm not sure if this is what you're trying to do here, but this is recommended substitution for the code you provided.

KreativeKai7-Feb-06 6:25

7-Feb-06 6:25

Thanks!! With your help I've taken my 32 warnings down to 6, and I'll keep working on the 6. Many more projects to convert up, but at least I have an idea how to figure out some of these warnings.

What is confusing is Microsoft wanted us to create an instance for everything, now they warn you that it isn't a good idea.

Thanks again! Smile | :)

Lost in the vast sea of .NET

Painting of usercontrols

Craster7-Feb-06 2:55