Re: 1 line of code that will crash the .NET2003 IDE/Compiler
From: Ken Halter (Ken_Halter_at_Use_Sparingly_Hotmail.com)
Date: 09/28/04
- Next message: Rarlfth Nadar: "Re: 1 line of code that will crash the .NET2003 IDE/Compiler"
- Previous message: Bob Butler: "Re: 1 line of code that will crash the .NET2003 IDE/Compiler"
- In reply to: Rarlfth Nadar: "Re: 1 line of code that will crash the .NET2003 IDE/Compiler"
- Next in thread: Rarlfth Nadar: "Re: 1 line of code that will crash the .NET2003 IDE/Compiler"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 28 Sep 2004 14:36:21 -0700
Rarlfth Nadar wrote:
> 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
You might want to read some of those... the same 'friendly shove' to a
more appropriate group can be found in all.
> I also posted (yes, I <gasp> cross posted) to the relevant DOTNET forums.
Nope... if you crossposted, the posts, along with all replies would show
here... instead, you multiposted.
> 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.
Again... crossposting is the best way to go. Place all target groups on
the 'Newsgroups' line at once, separated by a comma or semi-colon.
Exactly the same as sending an email to several people at once...
If you do this, no matter which of the 3 groups someone visits, they'll
see your post along with all replies... no matter which of the groups
actually contains the reply. It's actually a very nice feature and it's
designed to make it easy for everyone involved. The poster doesn't need
to visit several groups looking for answers and the people answering
don't need to spend time answering if answers already exist. Everyone wins.
> 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)
B# (VB.Net) just isn't VB... they share a few keywords and nothing more.
It's not our fault. We basically asked for VB6+ and B#'s what we got.
btw... the newsgroup doesn't specify a particular version because, until
recently, it really didn't matter. All we had to deal with was 16 vs 32
bit answers... and, instead of changing this several year old groups'
name to VB Classic Bugs or something similar, they left it alone and
created all new groups for .Net related issues.
Even though the following article's based on an earlier version (beta?),
some of it's still valid.
Visual Fred
http://www.mvps.org/vb/index2.html?rants/vfred.htm
> 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.
They've been redirected in almost every case.
> 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.
Note that you're not the first to get frustrated by redirection... and
note that Bob's reply wasn't targetted specifically at you... in fact,
here are 200+ instances of the exact same canned redirection.
Results 1 - 97 of about 267 for "This newsgroup is for users of Visual
Basic" group:*.vb.*. (23.35 seconds)
http://groups.google.com/groups?as_epq=This%20newsgroup%20is%20for%20users%20of%20Visual%20Basic&safe=images&ie=UTF-8&as_ugroup=*.vb.*&as_scoring=d&lr=&num=100&hl=en
btw... you won't be the last to get redirected either. Especially since
the ".Net" part of B# was dropped... now, it's VB 2005 (hopefully never
to be shortened to VB5)
Cheer up and don't take it personally. A stray .Net dev just might see
your post here. It'll never be removed. We just try to keep
conversations about .Net to a minimum to avoid confusion.
Rule 8f (link below)
"Assume that a reply is *not* meant as a personal attack"
Asking questions the right way
http://www.mvps.org/access/netiquette.htm#Asking
-- Ken Halter - MS-MVP-VB - http://www.vbsight.com Please keep all discussions in the groups..
- Next message: Rarlfth Nadar: "Re: 1 line of code that will crash the .NET2003 IDE/Compiler"
- Previous message: Bob Butler: "Re: 1 line of code that will crash the .NET2003 IDE/Compiler"
- In reply to: Rarlfth Nadar: "Re: 1 line of code that will crash the .NET2003 IDE/Compiler"
- Next in thread: Rarlfth Nadar: "Re: 1 line of code that will crash the .NET2003 IDE/Compiler"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
