VB6 and SourceSafe licences

long_b · 25-02-2015 9:21pm #1

We're still supporting legacy VB6 code and are still using SourceSafe (I know, I know ..)

Turns out the Visual Studio 2010 licences we have may not have "downgrade rights" to cover VB6.

We don't have MSDN subscriptions.

Given that neither VB6 nor SourceSafe licences can be bought from Microsoft, what are people in a similar situation doing for licences ?

jimmycrackcorm · 25-02-2015 11:18pm

you don't need to stick to SourceSafe, switch to subversion or git.

As for VB6 It's only an issue if you need to purchase new licences but maybe it's time to rewrite...

long_b · 25-02-2015 11:35pm

jimmycrackcorm wrote: »

you don't need to stick to SourceSafe, switch to subversion or git.

As for VB6 It's only an issue if you need to purchase new licences but maybe it's time to rewrite...

We need new licences for VB6 alright. We're moving off VSS but it will take time

amen · 26-02-2015 2:17pm

If you have VB6 you must have purchased a license at some. Does that license expired ?

long_b · 26-02-2015 4:12pm

amen wrote: »

If you have VB6 you must have purchased a license at some. Does that license expired ?

It doesn't expire but more than one person can use a physical disk I'm afraid

Tow · 27-02-2015 6:01pm

long_b wrote: »

but more than one person can use a physical disk I'm afraid

??

VB6 just uses a simple serial/number licence key. There is no expiry or checking number of machines it is already installed on etc.
If you download a copy from MSDN it defaults to a generic licence number (same for everyone), so no need to enter your own. If you need to buy additional licences to keep the bean counters happy then eBay (or shell out for MSDN) would be your only choices. But, if your problem is with licences for 3rd party controls from a company which no longer exists, you maybe into a whole world of pain.

VB6 and SourceSafe licences

Comments