Re: GP project setup utility?
- From: "Henning" <computer_hero@xxxxxxxxxxxx>
- Date: Mon, 20 Apr 2009 23:55:52 +0200
"Al Reid" <areid@xxxxxxxxxxxxxxxx> skrev i meddelandet
news:eHJgrxfwJHA.4324@xxxxxxxxxxxxxxxxxxxxxxx
"Henning" <computer_hero@xxxxxxxxxxxx> wrote in message
news:u6ruXnfwJHA.3848@xxxxxxxxxxxxxxxxxxxxxxx
Using VB.Net or VB Classic is not the issue. Is it so hard to let the VB
Classic users have this group for what it was created for. It has been a
really nice group for VB Classic, until for about one year ago. At that
time a few MVP's started to post replies to VB.Net Q's. They at the same
time also stated that there is nothing saying it is a VB Classic group.
And there is unfortunately not, only the time it has been only that. Even
Microsoft know that, and therefor started new groups for the dotnet
community.
And yes, I'm not naturally english spoken, if you find my writing hard to
understand. ;)
/Henning
My biggest problem is that *ANY* mention of .Net in this group turns into
a flame war. If someone is open to "upgrading" to vb.Net or is unsure
which way to go and it is suggested that VB.Net may be a viable option,
all hell breaks loose. If someone asks if VB or Delphi and someone
suggests that Delphi or Real Basic might be a good option, then all is
right in the world, no arguments or flame wars. Why is that the case?
VB6 and VB.Net are two very complementary products ant work well alone or
together and both offer the same friendly syntax we all use and love.
I think it's possible to have someone suggest VB.Net and not to start the
usual name calling, ranting and raving that always follows. Don't you? I
also think that a simple redirect is appropriate where the post has
obviously been misdirected.
BTW, your English is very good :)
--Al Reid
As I see it, it isn't as much someone suggesting VB.Net would be a better
choise, as the way of saying it. I don't expect this conversation we have
where VB.Net has been named many times will be flamed. On the other hand I
would expect that if a couple of others, CL or BMC, had this same talk.
There is, as we all say, nothing wrong with dotnet languages just for beeing
dotnet languages. It is the repeated postings of unrelated .Net replies to
Classic questions. For one of the MVP's it is also a fact that he is
posting, missleading replies, because he haven't a clue about the syntax
differences. Saying himself that he hasn't done much in VB Classic, not even
having it installed to test his suggestions before posting. Why post then?
This kind of stuff lowers the flamepoint of most materials, even people.
/Henning
.
- Follow-Ups:
- Re: GP project setup utility?
- From: Al Reid
- Re: GP project setup utility?
- References:
- GP project setup utility?
- From: Not Really Me
- Re: GP project setup utility?
- From: Michael Williams
- Re: GP project setup utility?
- From: Al Reid
- Re: GP project setup utility?
- From: senn
- Re: GP project setup utility?
- From: Al Reid
- Re: GP project setup utility?
- From: Henning
- Re: GP project setup utility?
- From: Al Reid
- GP project setup utility?
- Prev by Date: Re: GP project setup utility?
- Next by Date: Re: GP project setup utility?
- Previous by thread: Re: GP project setup utility?
- Next by thread: Re: GP project setup utility?
- Index(es):
Relevant Pages
|