Re: 1 line of code that will crash the .NET2003 IDE/Compiler

From: Rarlfth Nadar (someone_at_microsoft.com)
Date: 09/28/04 

Date: Tue, 28 Sep 2004 17:55:59 -0400

Jeez, this is really just WAY ridiculous, folks. (not directed at Ken, whos
last reply was very helpful)

Here's the fact. I'm not about to read a bunch of "netiquette" about how to
post, or about the differences between cross posting and multi-posting. It
just doesn't matter. What was the real intention of the replies to my post?

None of you folks own the space, machines, code, etc. that is used for this
or any other group. So if your original intention was to reduce clutter, or
bandwith, or space, etc. etc. etc, then probably just ignoring my post would
have served your purposes best. Instead, you felt the need to police me and
TOTALLY make me regret having posted anything at all here.

Granted, I'm not up on all the stringent "requirement" for posting in the
newsgroups, but I'm a damn good programmer, with a hell of a lot more
experience than the average Joe. I've got a lot of good info to offer, but
I'll be damned if I'm gonna listen to a bunch of jackasses tell me how to
appropriately offer help.

The info I offered originally may well save someone a hell of a lot of
frustration - simply because the may have read it in THIS group. If you
don't like it, well tough cookies.

Bob, you've totally succeeded at pissing me off, and guaranteeing that I
will NEVER post to this group again. So you can sit back, Bob, and pretend
that this is YOUR very own special newsgroup, where you are some
well-respected god of a dead language. The fact is that you're just too old
to learn dotnet, so you're taking it out on me.

Well, I'm off to try to salvage the day - Bob, drop dead, you old ***.

"Rarlfth Nadar" <someone@microsoft.com> wrote in message
news:uYzXlsZpEHA.1688@TK2MSFTNGP10.phx.gbl...
> Uh, ok, Bob.
>
> However, when you're done playing hall monitor, you might wanna look at
> all
> the other posts in this group related to VB.NET. I did, and that is why I
> though to post this (as I perceived) helpful information.
> I also posted (yes, I <gasp> cross posted) to the relevant DOTNET forums.
> And since I'll just bet that your the kinda guy that like explanations...
> Not all people are subscribed to all groups. So I posted in about 3
> groups
> so as to catch more folks - doggonnit! I just thought this was darned
> important enough.
>
> Oh, and in case you haven't noticed, the group name is
> microsoft.public.vb.bugs - What I posted was:
> A. For a Microsoft product
> B. Public
> C. Related to VB (the newsgroup doesn't specify a particular version)
> D. A bug.
>
> So as I (and probably most other folks who post VB.NET related stuff here)
> see it, my post was as "on topic" as the group name states, and only as
> "off-topic" as you, personally, state.
>
> So, keep up the good work, Bob - telling us all how that VB.NET bugs have
> absolutely nothing to do with VB. In the meantime, may all your DOTNET
> stuff crash.
>
>
>
> "Bob Butler" <tiredofit@nospam.com> wrote in message
> news:OeSDcdZpEHA.1952@TK2MSFTNGP12.phx.gbl...
>> "Rarlfth Nadar" <someone@microsoft.com> wrote in message
>> news:uF0Xz%23YpEHA.3252@TK2MSFTNGP14.phx.gbl
>>> Create a new solution, add a class...
>>
>>
>> --
>> <response type="generic" language="VB.Net">
>> This newsgroup is for users of Visual Basic and whatever
>> VB.Net is, Visual Basic it isn't. Solutions appropriate to
>> one will be meaningless in the other and you are more likely
>> to get the answers you need in newsgroups that are
>> frequented by others using the dotnet platform rather than
>> here where the focus is on VB "classic" . Look for
>> newsgroups with the words "dotnet" or "vsnet" in their name.
>>
>> For the msnews.microsoft.com news server, try these:
>>
>> microsoft.public.dotnet.general
>> microsoft.public.dotnet.languages.vb
>>
>> </response>
>
>
>