Can Visual Basic.net professional  2005 edition (Visual Studio.Net 2005
professional edition be installed on a Vista Home computer operating system?
If so, is there anything) I should be aware of?
  If not, can you tell me why Visual Basic.net professional  2005 edition 
professional edition does not run on a Vista Homer computer operating System?

Well, because some self righteous know it all thinks I'm full of BS and
should grow up, allow me to offer the fodder they need to justify their
distorted opinion:

This is not .NET newsgroup.  It's a newsgroup for Visual Basic, which is not
the same thing as VB.NET.  Not even close, regardless what a bunch of MSFT
sent stooges want you to believe.  Please refer future questions and replies
to any newsgroup that has ".net" in it's caption

[Pre-emptive reply to the .NET-heads]
Your momma.

Show quoteHide quote

This group is for VB (mainly v. 5 and 6). Your post
is about VB.Net.

  For VB.Net you can try the groups below, or any other
group with "dotnet" or "vsnet" in the name:

microsoft.public.dotnet.general
microsoft.public.dotnet.languages.vb
microsoft.public.vsnet.general

  If you are new to VB.Net, you need to know that there
are "two VBs" in use, which are entirely different beyond
their similar syntax. Likewise, there are two kinds of VB
newsgroups.

  Microsoft dropped ".Net" from the name "VB.Net" as
part of their marketing strategy to sell .Net to VB developers.
Adding to that confusion, VB.Net has been named with several
versioning systems. There is .Net v. 1, 1.1, 2 and 3. There is .Net
2005 and .Net 2008. And sometimes the VB.Net versions
are referred to as VB7, VB8 and VB9, even though VB.Net is
not a continuation of VB6! These days, anything other than
VB5 or VB6 is probably VB.Net.

  You need to be aware of the difference between "the two VBs"
when looking for newsgroups. The same applies when searching
for sample code. VB and VB.Net code can look very similar in
some cases, but code in one system is not applicable to the other.

Why are you still posting this nonsense ?  Numerous people have corrected
you on this numerous times.  Added to that the original poster clearly
stated they had "Visual Basic.net professional  2005 edition (Visual
Studio.Net 2005 professional edition)", so clearly the original poster knew
what product they have.

Are you posting misleading information on purpose to try to start yet
another silly pointless fight in here ?

Why are you still posting here, period?

Oh that's right.  MSFT has you on assignment.

For the record - anyone else reading this - nothing McCarthy claims is
accurate.  Visual Basic and VB.NET are not the same thing.  Not even close.
All this ego manic wants to accomplish is FUD.  Adding him to your ignore
list is highly recommended.

Kevin,

I think that you should change your policy.

Every search on MSDN newsgroups with visual basic or visual basic net direct
direct to this newsgroup.

I think that you have to build a newsgroup of your own.

Before you start shouting, it was not me who did this.
Microsoft hosts this newsgroup and they decided that.

Cor


Show quoteHide quote

.. . . and almost every search on MSDN for Visual Basic documentation leads
you to some Vb.Net crap. All part of the master plan to confuse people and
grab their money.

No, we should NOT. We already have a newsgroup of our own. This is it . . .

.. . . and we need to defend it from Micro$oft's attempts to destroy it by
swamping it with dotnet questions which, judging by what you have said,
appears to be deliberate.

Why don't Micro$oft just be honest about their intentions and simply close
the group down, and then we can all move to a group which they do not
control, such as comp.lang.basic.visual.misc

Mike

   Why didn't you post that to Bill McCarthy? Surely
you haven't failed to notice that after .Net people
get redirected -- often after their question is already
answered in the .Net group -- Bill McCarthy comes
through and "carpet bombs" those threads with
calculated ambiguity and discord?

   My posts attempt to make the situation completely
clear to lost DotNetters. Kevin's post was an attempt to
neutralize McCarthy's sowing of confusion. And why
are you here? Bill McCarthy is a DotNet troll, up to no
good, and there's not much we can do about that, other
than just hope that he eventually finds something more
useful, and less adversarial, to do with his time. Yet you
hang around, too. ... Why? ... To prevent us excessively
defaming .Net in the course of picking up after our troll?!

  If you want to protect the  reputation of .Net,
and you want to hang around here, then perhaps you
could take over the job of answering .Net posts with:

1) Clear redirection to the .Net group.

2) Some explanation of the difference between VB and
VB.Net, including an explanation of why the visitor ended
up in the wrong group, so that they understand the situation
in the future -- for both their sake and ours.

3) *No inclusion* of .Net advice, which should be saved
for the .Net group. (Generally it's harmless to answer a question
before redirecting, but in the case of .Net it's just too confusing
for everyone.)

   Then the rest of us could ignore the lost DotNetters,
and they would find the right group without stirring up
a debate.

Nonsense.  You *deliberately* posted the same nonsense you have been
corrected on by numerous people.  Your intent is not to help but rather to
sow anti .NET sentiment in a newsgroup that is for "VB".  Why is it we see
you, Provance and probably the other usual suspects continually jumping on
dotnet posts, usually posting inflammatory remarks rather than (a) answering
the OP and (b) redirecting them ?  I think it is because you want to wage a
silly anti .NET war.   Why is it you post the same nonsense ???




I don't see what Provance posts, but considering he steals people's
identities, continually changes his posting aliases, and generally is foul
mouthed, I doubt Provance added anything other than his usual personal
attacks.

LMAO!!  This coming from someone who uses my URL is their E-Mail address.
Must be a projection thing.  Or an Aussie scumbag thing.

It's a pity they didn't also know where to post their question! That's the
confusion which Mayayana was talking about, confusion that has been
deliberately fostered by the grinning Micro$oft fairground gypsies and by
your puppet master and, via the controlling strings, by yourself.

Mike

make sure your pc is plugged :O

Not really sure. A Homer computer operating system sound just about right
for dotnet ;-)

This is a Visual Basic newsgroup and the product you are using is NOT Visual
Basic, despite the name that was deliberately and dishonestly given to it by
the grinning Micro$oft fairground gypsies. Perhaps it won't run because
there is a three thousand billion gigabyte framework missing or something.
Visual Basic.Net is an imposter and it would be best if you posted your
question one one of the imposter's own newsgroups. For example, try:

    microsoft.public.dotnet.languages.vb

Mike

Hi Douglas,

AFAIK, it should install on Vista Home Basic.  There will be some issues
around not having IIS, but it should still install. Before trying again I
would make user you have all the latest Windows Updates.  If a re-install
doesn't work, try asking in one of the dotnet forums such as :

microsoft.public.dotnet.general
microsoft.public.dotnet.languages.vb





Show quoteHide quote

Too late as usual?

Expected the OP to stay an extra 18 hours just for U to show-up?

/Henning

Show quoteHide quote

I was too not aware that Microsoft has change the direction of the newsgroups.
I will add this newsgroup to my attention for the newer versions then VB6

Cor

Show quoteHide quote

Wanna bet ?

LOL.  Let me guess, now the new rules for here are no posts to be answered
unless in the first 18 hours ?





Show quoteHide quote

And regarding dotnet, not even after 18 hours. There are several M$
supported dotnet groups, thats the place to post'em.

/Henning

Show quoteHide quote

In your case let's make that 18 seconds! You repeatedly choose to answer
questions that have already been answered without adding anything of value
to the answers that have already been given, and you often deliberately do
so in an inflammatory way. You're a waste of space, McCarthy. Are you still
banned from the VB.Net group by the way? Considering that you have such a
great love for the imposter you're never on its newsgroup and apart from
just a few of occasions you haven't been there for many months, unless of
course you are hiding behind one of your aliases. Cut those strings,
McCarthy. Try to be a man for a change.

Mike

In your case let's make that 18 seconds! You repeatedly choose to answer
questions that have already been answered without adding anything of value
to the answers that have already been given, and you often deliberately do
so in an inflammatory way. You're a waste of space, McCarthy. Are you still
banned from the VB.Net group by the way? Considering that you have such a
great love for the imposter you're never on its newsgroup and apart from
just a few of occasions you haven't been there for many months, unless of
course you are hiding behind one of your aliases. Cut those strings,
McCarthy. Try to be a man for a change.

Mike

Piss off McCarthy. Just redirect the man and leave it at that. Cut the
strings, boy. Be a man instead of a puppet.

Help with Binary Compatibility
Fonts
(OT) false positives on my files
Can I loop through only SELECTED items in a multi-select FileListBox?
Internal String Visibility
Should I distribute Winsock?
Visual Basic Express 2008 Custom Error Message
Dynamic function calls
Problem with Display information in Labels
moving controls around on a form