I'm speaking of MS new APIs and products.
Yes, which are dropped after a few years, see e.g. VB.
VB.net is VB on steroids in my opinion.
This doesn't help people losing their old code base. People followed
another Microsoft hype and now they are lost.
I didn't have problem transition my clients VB6 project from Win32 forms to
ASP.net WebForms, I just separated it's GUI from its logic, then transcoded
the GUI design to XML and converted the XML to ASP.net (.aspx) pages via XSL
stylesheets (can get that technology of mine from
http://tranXform.onestop.net), but I could have imported it to VB.net as is
if we didn't want to make it an ASP.net web application, but keep it a
desktop app (using WinForms) or have it run at rich clients (e.g. inside IE
using WinForm controls).
There are various third-party options too to help one transition to VB.net
and they can also stay on VB6 if they wish for some old project or keep
parts of it in VB6 (say if they author ActiveDocuments) and move parts to
VB.NET, since .NET supports COM and OLE/ActiveX controls too.
========================
George Birbilis ([EMAIL PROTECTED])
Microsoft MVP J# 2004-2006
Borland "Spirit of Delphi"
http://www.kagi.com/birbilis
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
