'My' object issue

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,

I am using VB.NET 2005 on two PCs. On 1 PC, if I type 'my.', the
intellisense shows the list of members (computer, etc.). On the 2nd PC, I do
not get the list and the error list shows "Name 'my' is not declared.

If I open the project with the 1st PC, I can use my object.

Am I missing something? How do I fix it?
 
Hello,

I am using VB.NET 2005 on two PCs. On 1 PC, if I type 'my.', the
intellisense shows the list of members (computer, etc.). On the 2nd PC, I do
not get the list and the error list shows "Name 'my' is not declared.

If I open the project with the 1st PC, I can use my object.

Am I missing something? How do I fix it?

Have you rebuilt the entire solution?

Thanks,

Seth Rowe
 
Hello,

I tried to rebuild the solution but the error keeps preventing a successful
build. This error happens also when I am creating a new application.
 
Hello,

I tried to rebuild the solution but the error keeps preventing a successful
build. This error happens also when I am creating a new application.

--
Thanks,
LDV-ME






- Show quoted text -

You might comment out the line if possible and then rebuild - many odd
errors clear out when the app is forced to update it's references.

Also I'm thinking there is an option to turn off the "My" object - I'm
not sure if I saw it, and I'm not sure where it was if I did see it.

Thanks,

Seth Rowe
 
If I comment out the line, I can build the solution but it will not work as
expected. I have to replace the lines where I use the My object with multiple
lines to perform the same operations. This is not the optimal solution. I
would prefer to use the My object even because the code would be cleaner.
 
If I comment out the line, I can build the solution but it will not work as
expected. I have to replace the lines where I use the My object with multiple
lines to perform the same operations. This is not the optimal solution. I
would prefer to use the My object even because the code would be cleaner.

I think you misunderstood - I wanted you to comment out the line,
rebuild, and uncomment the line. I was hoping a full rebuild would
force the application to update it's references and rediscover the
"My" object.

As far as optimal goes, I don't think using "My" will net you any
advantages. (IMO) It is another one of Visual Basic's "shortcut"
keywords that just saves you from a bit more typing. As far as cleaner
code goes - thats a personal preference.

By the way, have you readded the Visual Basic reference that contains
"My" to your project yet?

Thanks,

Seth Rowe
 
Sorry, my fault.

I tried different times to comment the lines, build, and uncomment them
without luck.
 
Has anyone have other suggestions? I am still experiencing this issue.

--
Thanks,
LDV-ME








- Show quoted text -

Did you readd the Visual Basic reference?

Thanks,

Seth Rowe
 
Back
Top