I'm still using Visual C++ 6.0, haven't even had a chance to look at .NET,
but from what I hear, it's C# this and VB.NET that, with no hot talk about
Visual C++ .NET or ATL.

Maybe I'm just not hearing from the right sources, but I assume ATL will
still play a pretty large role in Microsoft development efforts going
forward?  My only hesitance in asking that is since ATL is so closely
associated with COM that there might be a movement away from ATL and that
"old" programming model (even though .NET isn't officially released yet).

Anyhow, if anyone's heard some good things about ATL's future or has some
article links on what's in store for it in .NET, I'd appreciate it.  I'd
hate to think my dearly-bought knowledge of BEGIN_COM_MAP() might go to
waste!  ;)

Thanks,

    Jimmy

We have also introduced a set of server side classes and framework for ATL,
usually referred to as ATL Server. These classes lets you write Web
applications and Web services with the ATL programming style very quickly.
And these classes can also be used outside of the Web application/service
framework.

--
Anson Tsao
Visual C++ libraries team

Of course, this posting wouldn't be complete without a nice, juicy
disclaimer from our lawyers: This posting is provided "AS IS" with no
warranties, and confers no rights. You assume all risk for your use. ? 2001
Microsoft Corporation. All rights reserved.

http://www.idevresource.com/com/library/bytesize/atlserver.asp

1) How does C# come into play. Does this effectively supplant C++, COM and
ATL for all intents and purposes since it will be much easier to work with.
That is, even though the former will still be supported, what will be the
point if C# is really that much easier.
2) For those of us hell-bent on sticking with C++, COM and ATL (after much
pain learning them), how steep will the learning curve be in the new .NET
world. That is, how drastic are the changes and how much new info will we
have to learn (to continue to work with them). I ask as a seasoned developer
(18+ years) since the glut of technology really has to stop. It's largely
responsible for the substandard state of so much 3rd-party software these
days. It's impossible for even the most experienced developer to get a
handle on things and we can't keep throwing out what we've learned every few
years only to become "experienced" rookies all over again (there are a dozen
complex ways to do almost everything these days). I'm nevertheless a great
supporter of MS but in your unofficial capacity, can you offer any
reassurance to alleviate the concerns of myself and many other developers.
3) Do you know anything about the future of OLE DB and ADO in particular.
What's its place in the new order.

Any info you can provide would be welcome. Thanks.