flynnibus
09-15-2010, 01:20 PM
I checked the FAQ and did not see this answered... so here goes.
Previously, vb.com used a running contract model.. you had to be licensed with vb.com to have access to d/l stuff from vb.org
But with vb's new 'buy one release, and its yours' pricing model - the only running state is paying for technical support - we have a perpetual license for the major version we buy.
What will vb.org follow for it's member access levels?
What about vb3.x users who have a valid vb4.x license via their previous license, but did not buy vb4.0 explictly?
Thx
Previously, vb.com used a running contract model.. you had to be licensed with vb.com to have access to d/l stuff from vb.org
But with vb's new 'buy one release, and its yours' pricing model - the only running state is paying for technical support - we have a perpetual license for the major version we buy.
What will vb.org follow for it's member access levels?
What about vb3.x users who have a valid vb4.x license via their previous license, but did not buy vb4.0 explictly?
Thx