advice on ADO-->ADO.NET, COM/DCOM.....
I already have some experience on COM, Active X controls, and ADO programming,
but not an expert.
As most issues keep emphasizing, COM/DCOM will become legacy code after .NET
release, and there will be huge difference between ADO and ADO.NET. I am
wondering do I need to stop learning more on those current technologies,
if migration issue is not a concern.
Re: advice on ADO-->ADO.NET, COM/DCOM.....
"Jerry" <Jthoa@freeemail.com> wrote:
>I already have some experience on COM, Active X controls, and ADO programming,
>but not an expert.
>As most issues keep emphasizing, COM/DCOM will become legacy code after
>release, and there will be huge difference between ADO and ADO.NET. I am
>wondering do I need to stop learning more on those current technologies,
>if migration issue is not a concern.
From what I can make out of the video archive at MS, your fears seem to eminate
from being uninformed. IMHO, you only need to use the .Net platform if you
are writing .Net applications. Otherwise, you can just look at .Net as a
tool that is designed to increase programmer productivity yet again. If
you are running a subscriber-based .Net type of application then you could
do it more quickly using the .Net platform. The computers that that application
converses with, it seems, only need to provide their data in an XML format;
they do not also need to be running a .Net platform. I am only an amateur
myself so don't quote me on any of this. It seemed in the MS videos that
they were almost preaching apologetics on the interoperability of .Net with
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL