I agree with you about a long time for VB6 code to disappear, but that is completely separate from VB.NET code.
I credit even feeble-minded VB developers with the vision to generally not even think about porting VB6 code to VB.NET (if not, I don't want to know them on a professional basis). Apart from the name, it's a completely different beast. I don't believe there will be wholescale porting of VB6 code to .NET, therefore I strongly believe you will find way more than single-digit C# development being undertaken. I don't believe VB developers are blindly going to just use VB.NET without at least some of them opening their eyes to the possibility of another .NET language. C. -----Original Message----- From: Neven MacEwan [mailto:[EMAIL PROTECTED] > I find that statement a bit hard to believe. Why? > What do you base that on? Based on the fact that there are several million VB programmers out there and billions of lines of VB code, It will take a long time for that to get out of the system (see recent threads about COBOL & FORTRAN). The logical jump is a/ We have a VB App b/ Lets port it to VB.net 'cause Bill told us too c/ Hey there this thing called Middleware..we can make our app n+ tier, the Marketing guys said its good d/ I can write this in VB too! ----- Original Message ----- To: <[EMAIL PROTECTED]> Sent: Tuesday, January 27, 2004 11:28 AM Subject: RE: [DUG] [OFF-TOPIC] Delphi 8 and .net > I don't think it's necessarily going to be Delphi.NET, but I'd have > thought C# would account for way more than single digits. Oh yeah, that > and Cobol.NET... > > Cheers, > > C. > > -----Original Message----- > From: Neven MacEwan [mailto:[EMAIL PROTECTED] > > Also don't forget that 90% of .net code will probably end up being > written in VB _______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi
