I heard through the grapevine yesterday that MS said (maybe as long as 6
months ago) they will continue to support VB6 (by popular demand). It
has breathed new life into one of my 5 year old products. It might have
lived anyhow but the rewrite cost was going to be enormous.
Chuck Norcutt
Allan Mee wrote:
> Just d/l it - and yeh, it is very nice :)
> I'm going to write some imaging software soon - it's been about a year since
> I last did any serious coding - I've been too busy doing other stuff and I
> really do need to get stuck into VB.Net - everytime Ive tried VB.Net, I've
> ended up thinking that this (whatever I'm doing) is a cinch in VB 6.0 and
> ended up coding in VB 6.0 - and I really do need to make the transition. Ok
> I'm too old (turned 50+) to go back into full-time employment as a VB
> programmer again, but it woiuld be nice to get to a point where I can tackle
> any project in VB.Net (which is a *very* different animal to VB 6.0). I've
> programmed (commercially) in VB 3.0, 4.0, 5.0 and 6.0 - all of which were
> 'natural' progressions. VB.Net is a kinda 'unnatural' progression - because
> MS changed VB so much with VB.Net
> Allan
==============================================
List usage info: http://www.zuikoholic.com
List nannies: olympusadmin@xxxxxxxxxx
==============================================
|