Bob,
Rush to my aid (chuckle) -- this is a newsgroup nobody 'rushes' to anyone's
aid. And M$ is universal acceptance of Microsoft -- hell you even
recognized it. Anyway, I "rushed" to my own aid and found a workable
solution to the bug and posted that solution so that other's could benefit.
But as with everything .NET/VS 2005 -- most of my time is spent searching
for work arounds and less actually being productive.
Sorry you don't like the post, but I've endured VS hell for too long and I'm
done giving M$ the benefit of the doubt -- "good work boys & girls, but it
needs a little help" -- I'm just over repeating that same line everytime M$
release their next "best" thing. It is time to say "what is this crap!"
Fix the crap and no more "give it your best try" and no more releases to
meet some target date. If it don't work, don't release it. Have you seen
the active bug list for VS 2005 -- OMG!! These aren't just "little" issues
either.
But the key point is, if M$ need to take this long to produce a workable
product (and no VS 2005 is still very much beta), shouldn't M$ be asking
themselves WHY IS IT TAKING THIS LONG? Geee, just maybe, just possibly,
they've dug their own hole and just possibly, their concepts of "how it
should be done" are really completely worthless?
I'll advocate anyone that does it well enough -- VS 2005 isn't even close to
that yet -- given the resources at M$ that is pretty sad. Even the
developers that are trying to be "nice" to M$ are having a hard time saying
the "love everything about VS 2005" -- many are saying some good, some bad
and that is being "nice". I'm personally over being "nice" to M$ as it has
ZERO positive affect, they've got the resources, make this crap work and do
it quickly.
Rob.
"Bob Lehmann" <no****@dontbotherme.zzz> wrote in message
news:eB**************@TK2MSFTNGP05.phx.gbl...
I'm sure the use of $ in MS will encourage many of the users in a MS
newsgroup to rush to your aid. Good strategy!
Maybe someone in the java or linux advocacy groups will lend a hand since
they speak your language.
Bob Lehmann
"Rob R. Ainscough" <ro*****@pacbell.net> wrote in message
news:Ox**************@TK2MSFTNGP02.phx.gbl... I found a work around to this "bug" which M$ claim is not a bug and have
opt'd to ignore it.
https://connect.microsoft.com/Visual...edbackID=90564
The real issue is why are my reference consistantly getting messed up --
which is what is causing this problem that is not actualy related to the
Windows Form -- it just so happens the loading triggers this error even
though there is no actual reference made to these "cautioned" references.
Rob.
"Rob R. Ainscough" <ro*****@pacbell.net> wrote in message
news:eq**************@TK2MSFTNGP05.phx.gbl... > I've started getting this error now when I load my solution and do a
> Build. Rebuild doesn't resolve it. Any suggestions?
>
> I suspect one of the hotfixes, but can't confirm.
>
> Rob.
>
>
>
