Thanks for the reply Miha!
Again, the object in question is excluded from the project. (Right click on
object in Solution Explorer, 'Exclude From Project' is checked.)
So what should it matter if the schema is good or bad...?
(I think this problem occurs directly after removing something from the
project. But it doesn't go away unless I reboot the IDE...)
-------------
Unrelated, but FYI:
I did have one incident where this was happening with an object that IS
included in the project. Reading your suggestion about schema errors
prompted me to get to the bottom of this problem once and for all. The
problem wasn't schema errors though. It was that, somehow, there was
another .vb file of auto-generated code for the same dataset already in the
project. But it had somehow become un-parented from its original dataset,
and was hiding under another one! (Possibly via an accidental drag & drop
by me...) The only way I found it was as a result of manually running the
custom tool on the proper dataset. When I did so, it generated another
class that conflicted with the orphaned one, so I was able to use compiler
errors on the task list to zero in on where this conflicting class
declaration was coming from.
Now the big question is... how long have I been basing my debugging on the
wrong version of the class?!?!?! =)
Miha Markic said:
Huh?
Your scheme might contains errors.
--
Miha Markic [MVP C#] - RightHand .NET consulting & software development
miha at rthand com
www.rthand.com
lover said:
That's great to know...
But why is it giving me this error for items that are supposed to be
excluded from the project???
Annoying! >=|
