where is the real VB group?

[aaron.kempf]

hey I went to Microsoft.Public.VB today and google says
You cannot post messages because this group is only available as an
archive.

I'd like to know where the real VB newsgroup is?
I surely don't really write VB.net for the most of the stuff i do.. I
do use Vb 2005 for some things and Vb 2008 for some things..

But I mainly write VB in Outlook, Access, Excel, Word and Visio.. I
just don't know where I can go to ask questions.

Thanks

-Aaron

 

[Harry]

hey I went to Microsoft.Public.VB today and google says
You cannot post messages because this group is only available as an
archive.

I'd like to know where the real VB newsgroup is?
I surely don't really write VB.net for the most of the stuff i do.. I
do use Vb 2005 for some things and Vb 2008 for some things..

But I mainly write VB in Outlook, Access, Excel, Word and Visio.. I
just don't know where I can go to ask questions.

Thanks

-Aaron

Try microsoft.public.vb.general.discussion

 

[jaydeflix]

Try microsoft.public.vb.general.discussion

Ok, Google Groups seems to have eaten my post, so let me try again...

For the application specific questions, I'd go to:
microsoft.public.outlook.program_vba
microsoft.public.word.programming
microsoft.public.excel.programming
microsoft.public.visio.developer
and, as for Access, I'm not entirely sure which Access group is
right.

 

[Cor Ligthert[MVP]]

Aaron,

There are no newsgroup which covers program language families.

As VB is a family of program languages which covers

Visual Basic for Applications
Visual Basic Script
Visual Basic for Net
Visual Basic (Classic)

You hopefully will understand that there are more newsgroups.

This newsgroup is for the program language VB for Net (dotnet.VB)

Cor

 

[aaron.kempf]

I don't get it Cor.

Why doesn't this address Microsoft.Public.VB refer to Vb 2008?

It's not called VB DOTNET is it? Isn't it just called VB again? And it
was just called VB in the last version, 2005!!

Why should Microsoft kill off a newsgroup that refers to 3/4 of the VB
family?
I just don't get it. The product is called VB why do they have to
change the newsgroup name?

Yes; it is a big deal!

Maybe I'm just the only person that notices a difference-- maybe you
guys didn't have to take a mareting class in college. I don't know.

I just think that they are confusing people..

Ok real quick.. if I refer to C# what am I referring to? Does it
matter if I'm referring to 1.0 or 1.1 or 2.0 or 3.0 or 3.5?

Why does VB have _SO_ many different newsgroup names? and most
importantly; the main prominent newsgroup is retired?

That just makes it look like VB is DEAD.

-Aaron

 

[Cor Ligthert[MVP]]

Aaron,

That 3/4 is absolute not true anymore. However, I have asked this once as
well.

The answer is simple there are to many links (not only at Microsoft)
referencing to this newsgroup that using a new name would break that.

Beside that has the classic VB community a very well knowed name in kicking
everybody out or abuse somebody who wants to ask something about VB for Net.

Cor

<[email protected]> schreef in bericht
I don't get it Cor.

Why doesn't this address Microsoft.Public.VB refer to Vb 2008?

It's not called VB DOTNET is it? Isn't it just called VB again? And it
was just called VB in the last version, 2005!!

Why should Microsoft kill off a newsgroup that refers to 3/4 of the VB
family?
I just don't get it. The product is called VB why do they have to
change the newsgroup name?

Yes; it is a big deal!

Maybe I'm just the only person that notices a difference-- maybe you
guys didn't have to take a mareting class in college. I don't know.

I just think that they are confusing people..

Ok real quick.. if I refer to C# what am I referring to? Does it
matter if I'm referring to 1.0 or 1.1 or 2.0 or 3.0 or 3.5?

Why does VB have _SO_ many different newsgroup names? and most
importantly; the main prominent newsgroup is retired?

That just makes it look like VB is DEAD.

-Aaron

 

[aaron.kempf]

well then we move the VB6 people to microsoft.public.vb.Com

Why should we distract millions of developers every yeah just because
they mis-named Visual Basic during 2002 and 2003.

Now it is called VB 2005 and VB 2008; I don't think that the 'main
channel for talking about VB 2008' should be called
microsoft.public.dotnet.languages.vb

I think that Microsoft should simplify VB. The VB newsgroup should be
about VB.

Anything else is just hogwash I think.
I just think that Microsoft-- with the release of VB 2008 - should
simplify simplify simplify VB.

I don't mean -dumb it down- I just mean.. 'take down the billboard
that says VB is dead'.

I believe that changing microsoft.public.vb to an 'archived group' is
just like a billboard that says 'VB is dead'.

Thanks

-Aaron

 

[aaron.kempf]

and I don't know what you're talking about.

there is no such thing as 'kicking people out of a newsgroup'.

There are complaints.

But nothing like the complaints from hearing 10 millon VB developers
wake up and say 'oh vb is dead'.

Nothing like the screams of millions of professional developers-- who
choose to use VB because it is the best, most portable language
anywhere.

I can't run C# code in a SQL Server DTS package.

I dont' think that VB is dead.

I love the new VB 2008. Honestly.. It's finally almost usable again.
I just think that we should

legalize talking about vb 2008 in microsoft.public.vb

-Aaron

 

[Herfried K. Wagner [MVP]]

well then we move the VB6 people to microsoft.public.vb.Com

I don't think it's necessary to rename/remove/add newsgroups for Classic VB
and VB.NET. The existing newsgroups are well-established and have their own
groups of users. Posts belonging to another newsgroup are kindly redirected
to the newsgroup they belong to.

However, Microsoft could make some improvements:

* Unfortunately 'news.microsoft.com' does not make use of newsgroup
description strings, which could remove ambiguity by listing product names
in them.

* The right newsgroups must be linked on the right place. AFAIS Microsoft
is doing a good job here -- the VB.NET website listed recent posts from this
group recently.

Now it is called VB 2005 and VB 2008; I don't think that the 'main
channel for talking about VB 2008' should be called
microsoft.public.dotnet.languages.vb

Well, the main problem is IMO not the name of the newsgroup, it's the
problem that Microsoft gave two different technologies (Classic VB, VB.NET)
the same name. This will always lead to confusion, regardless of how the
newsgroups are named.

 

[aaron.kempf]

I disagree.

They stopped calling it vb.net what 3 years ago?

They killed microsoft.public.vb and it looks to me like 'vb is dead'.

I _LOVE_ the next vb 2008-- it's finally a usable product.. I mean it
launches in less than 30 seconds!

I just --still-- think that it's a load of hogwash that
Microsoft.public.vb doesn't refer to vb (2008)

-Aaron

 

[Armin Zingler]

I just --still-- think that it's a load of hogwash that
Microsoft.public.vb doesn't refer to vb (2008)

m.p.vb is for VB classic questions.
m.p.d.l.vb is for managed VB questions.

That's the definition of the group content. Read the definition and
you'll know where to post the questions. That's all that has to be said
about it.


Armin
PS: Maybe it helps if you read the "dotnet" in this group's name as
"managed". Is VB 2008 managed? Yes, it is. So, where to post VB 2008
questions? ...... Correct! In this group.

 

[jaydeflix]

Herfried, when I was there, I tried to get that fixed. Unfortunately,
there were some technical limitations that prevented it from an easy
solution and my budget was... well... I actually didn't have one. If
you really want to know the details, I can share them, but I don't see
it ever getting fixed, especially now that no one seems to care about
the newsgroups in-house. Scratch that. No one who is in any position
to do anything about the newsgroups from a meta standpoint care enough
about the newsgroups.

They killed microsoft.public.vb and it looks to me like 'vb is dead'.

Aaron,

They didn't kill microsoft.public.vb. That group never, afaik,
existed on the Microsoft newsgroup servers, and if it did, it didn't
last for long.

The microsoft.public.vb.* hierarchy, otoh, does exist and continues to
exist and, last I checked, was quite busy.

 

[aaron.kempf]

I'm sorry what definition are you talking about?

seriously?

I don't see anything other than m.p.vb is dead

-Aaron

 

[aaron.kempf]

wow. now i've never heard that one before.

so how can I create a group on microsoft.public without microsofts
approval?

ROFL

-Aaron

 

[Armin Zingler]

I'm sorry what definition are you talking about?

seriously?

I don't see anything other than m.p.vb is dead

-Aaron

The definition of the content of the groups mentioned. Read m.p.vb as
m.p.vb.*. They are not dead. There is no m.p.vb @ news.microsoft.com.


Armin

 

[aaron.kempf]

there is no microsoft.public.vb?

again you're arguing either
a) the site never existed
b) it was killed off

which is it?

either way; it's a stupid policy.

It hasn't been called VB DOTNET in what 4 years? I don't think that we
should make the VB Group look like a dead end.

-Aaron

 

[aaron.kempf]

news.microsoft.com?

the nntp server?
ROFL

as if I'd _EVER_ use that they block peoples' post when they criticize
Microsoft.

I mean; I thought the gestapo died back in WW2.. lol

-Aaron

 

[Armin Zingler]

news.microsoft.com?

the nntp server?
ROFL

as if I'd _EVER_ use that they block peoples' post when they criticize
Microsoft.

I mean; I thought the gestapo died back in WW2.. lol

-Aaron

Block posts? *LOL* Then I would not have been able to post for years...
Yes, this is a newsgroup if you haven't noticed it yet, and a news
server hosts newsgroups. What's so funny with it?


Armin

 

[aaron.kempf]

what's funny?

they killed the vb group and it looks to me like 'VB IS DEAD'.

I don't think that is good for my career.

-Aaron

 

[Herfried K. Wagner [MVP]]

wow. now i've never heard that one before.

so how can I create a group on microsoft.public without microsofts
approval?

The group 'microsoft.public.dotnet.vb.general' also exists/existed, but it
has (IMHO) never been created by Microsoft.