Lloyd
I may be wrong, but I think that the OPTION STRICT setting in the IDE
options dialog is not designed to cause the clause to be created in new
classes. Rather, it is a default to apply in the absence of an explicit
declaration at the top of the file.
That said, I know what you mean about the IDE. For the most part it works
fine, but I also frequently get erroneous errors reported, which disappear
on a repeat build or closing and restarting the IDE.
One thing I would say is that I have found some of the apparently erroneous
errors reported to be caused by complicated linkage in multi-project
solutions. If coupling is high, the IDE gets 'confused' about from where to
satisfy references. This is made worse if names are re-used in different
projects. Even if the declarations are the same they will have different
signatures, and therefore may lead to confusion. I have stared at an
unexplained error for hours, convinced that it is not an error, only to
realise later that I had used the same control name or namespace in two
projects, and that the compiler was getting its reference from one place
whilst I was expecting it to get it from another. Qualifying the reference
sorted the problem (although changing the name was ultimately the best
solution).
If you have a multi-project solution, you could look carefully at the
Reference Paths set up in each project, and ensure they are consistent with
the project inter-dependencies set up in he solution explorer.
I am not suggesting that this will completely cure your problems, but I
found that the incidence of erroneous errors falls off when coupling is low
and inter-dependencies are minimised.
HTH
Charles
"Lloyd Sheen" <sq*******************@tostopspamhotmail.com> wrote in message
news:kc****************@twister01.bloor.is.net.cab le.rogers.com...
Yes but there are MS lurkers. Perhaps they will get the message to fix
the IDE before they release another one with so many problems.
Even things like setting OPTION STRICT ON does not work. Create a new VB
class and the OPTION clause is not generated.
Lloyd Sheen
"Michael S" <a@b.c> wrote in message
news:%2******************@TK2MSFTNGP12.phx.gbl... "Lloyd Sheen" <sq*******************@tostopspamhotmail.com> wrote in
message news:0t********************@news01.bloor.is.net.ca ble.rogers.com... So MS where is the error that is reported on last line
Please, LLoyd. This is a developer-community, not Microsoft support.
