Re: Acquiring VB3 - Licensing
- From: "Scott M." <s-mar@xxxxxxxxxxxxx>
- Date: Thu, 1 Oct 2009 13:36:05 -0400
"Nobody" <nobody@xxxxxxxxxx> wrote in message
news:%23k5Y$wrQKHA.4028@xxxxxxxxxxxxxxxxxxxxxxx
"Scott M." <s-mar@xxxxxxxxxxxxx> wrote in messageWell newer tools and software requre getting/having keys before the software
news:OwfGM1qQKHA.4028@xxxxxxxxxxxxxxxxxxxxxxx
"Peter T" <peter_t@discussions> wrote in message
news:O69S58pQKHA.764@xxxxxxxxxxxxxxxxxxxxxxx
"Jason Keats" <jkeats@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OpJCZSeQKHA.5068@xxxxxxxxxxxxxxxxxxxxxxx
MSDN Pro (etc.) allows you to download VB 2, 3, 4 & 6.
I notice no product key is required for VB 2, 3 & 4 (unlike 6), not
quite sure how to interpret that with respect to license.
In MSDN, no license key is needed for any of the development tools
because it's baked into the installation package.
-Scott
Just in case of some misunderstanding, some older development tools don't
require keys. Newer tools and software require getting keys before the
subscription ends, otherwise the newer tools cannot be installed.
is installed (not before subscription ends because many subscriptions allow
the software license in perpetuity). It's just that these tools, when
gotten via an MSDN subscription are what MS calls: "pre-piddled" meaning
that the key is baked into the software's installation package and when the
screen comes up that asks for the key, it's already filled in and greyed out
so it can't be altered.
-Scott
.
- Follow-Ups:
- Re: Acquiring VB3 - Licensing
- From: Karl E. Peterson
- Re: Acquiring VB3 - Licensing
- References:
- Re: Acquiring VB3 - Licensing
- From: Peter T
- Re: Acquiring VB3 - Licensing
- From: Scott M.
- Re: Acquiring VB3 - Licensing
- From: Nobody
- Re: Acquiring VB3 - Licensing
- Prev by Date: Re: Acquiring VB3 - Licensing
- Next by Date: Re: WildCard
- Previous by thread: Re: Acquiring VB3 - Licensing
- Next by thread: Re: Acquiring VB3 - Licensing
- Index(es):
Relevant Pages
|