Re: Petition again MS

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Bill,

It's not only about respect for the posters, but respect for the newsgroup
as well. There is a reason the existing VB groups remained for VB 6 and
earlier while VB.net (and all dotnet flavors) got their own shiny new
groups... continuity and consistency. Even if you feel VB.net is a
continuance of VB, there is enough a difference in just syntax and such to
warrant seperate groups.

Say someone asks a VB 6 question, someone else then post a solution like...

If String.IsNullOrEmpty(PictureFile) = False Then
MyPicture.Image = Image.FromFile(PictureFile)
MyPicture.Size = MyPicture.Image.Size
End If

.... the OP gives it a try and discovers it doesn't work in VB 6. Both the
OP and replier just wasted time, and maybe someone else doesn't post a valid
solution because they were only glancing the thread and saw someone replied.
Someone else following the thread, excited with a posted solution, also
discovers it doesn't work in VB 6. Someone else a few months from now
searching the UseNet archives uncovers the post and tries the replied
solution only to discover it doesn't work in VB 6. Etc. and so on...

Sure, the above code is simplistic, but it's just for the sake of example.
So imagine how confusing it would get for more complex coding issues. And
how confusing it would get to have a mixture of VB 6 and VB.net code in the
group and archives. This is why the pre-existing VB groups remain VB 6 and
earlier while dotnet got their own new ones (and why dotnet questions get
pointed to the dotnet groups). To avoid confusion and maintain the
continuity of the archives.

Is the issue with the dotnetters that redirections sometimes are a little
snarky? I haven't been in the dotnet groups so I wouldn't know firsthand...
do all VB 6 questions get redirected from the dotnet groups sans snarkiness?

Is the reason some dotnetters come to the classic VB groups to troll and
stir the pot because they are upset that the old VB groups didn't become
VB.net and classic VB didn't get the new groups like
microsoft.public.vb.old?

If you love VB.net, then great. Help and contribute in the VB.net groups.
If others prefer VB 6 for whatever reason, so what? If some classic VB'ers
feel betrayed by MS, what does it matter to you (unless you are under MS
employ)? Unless you're getting some sort of prize or reward for each
classic VB'er you convert, there is no reason to come to the classic VB
groups for the sake of stirring up shit unless it's for attention or
self-entertainment, and thus the definition of trolling. Michael Cully
falls into this "troll" category, as does anyone else that comes here just
to stir up shit.


.



Relevant Pages

  • Re: Wasnt dotNet supposed to be a multi-platform alternative to Java?
    ... Borland creating a Delphi Compiler for dotNet for one reason and one reason alone. ... That is, Windows 98, Windows ME, Windows NT, Windows 2000, ...
    (borland.public.delphi.non-technical)
  • Re: One thing I noticed
    ... > Practically all of us who are stuck in VB6 are stuck for the same reason. ... > maintaining that app ten years from now, and if there is no budget for a ... > re-write, that means I am stuck with VB6 for the forseeable future. ... All tests I have done have demonstrated dotnet ...
    (microsoft.public.vb.general.discussion)
  • Re: Ideas for projects
    ... A bit offtop - what's the reason for this? ... Need some area to master your knowledge and have no idea or what? ... I thought I saw a website where people submitted ideas ... e> purpose is for novice dotNET developers to get to know dotNET. ...
    (microsoft.public.dotnet.general)
  • Re: Myths of our time...
    ... There might be a reason why Windows Longhorn whatever, is not written in dotNet:) ... >> If we apply the same skills to writing code the traditional way, ...
    (borland.public.delphi.non-technical)
  • Re: Performing Ping from within VB.Net
    ... Preserving the continuity of the archives. ... >> Then why are the newsgroups specific to DotNet? ... >> questions from VB and VB.NET, and thus eliminate alot of confusion. ...
    (microsoft.public.vb.general.discussion)