Support Policy for ATL Server Library

Support Policy for ATL Server Library

  • Comments 8

Recently the VC++ team released ATL Server as a shared source library on  to allow its user community to enhance the library in different directions and at a faster pace than we are able to support. Since then we have received some questions about how this impacts the support policy for ATL Server. The impact of releasing ATL Server can be summarized in three bullets:

1.       ATL Server library and related tools included in VS2002, VS2003 and VS2005 will continue being supported by VC++ team as long as these releases of Visual Studio are supported. Basically releasing ATL Server on has no impact on support policy for VS2002, VS2003 and VS2005. You may also find more details on time period during which a version of Visual Studio you are using is support on Microsoft Support Lifecycle site.

2.        ATL Server is no longer under active development by the Visual C++ team and will not be included in VS2008 or any future version of Visual Studio.  Future development of ATL Server will be done as part of a shared source project on,  If you are interested in contributing to this project or wish to request a new feature in this version of library, please contact the coordinators of the project on

3.       Because ATL Server is now a community project, Microsoft will not offer product support for building applications using the version of the ATL Server library or with integrating this library with any version of Visual Studio or Visual C++ Express.  To receive guidance or help on steps required for integration of the shared source version of ATL Server with any Visual Studio version you use, please contact coordinators of the project on

If you have any questions, please send us email or leave them in comment for this post.


The Visual C++ Development Team

  • That's a shame.  For the most part, unless you're involved with the open source project from the very start, that removes the technology from mainstream use.

    I've had to deal with making use of several open-source projects.  Support is horrendous.  If you find a bug, you rarely get any support and, unless you're on the project from the start, if you have a fix it's rarely accepted.  This leaves you branching from the trunk and making integrating any future changes difficult or impossible due to time and delivery constraints.

  • Since it certainly seems like it is all now dropped from a pretty tall building, what do you expect to tell people wishing to utilise IIS 7.0 features or any future version of IIS from C++?

    - "Relax and forget it? GoTo CodePlex, wait a 3 months?"

    - "Adopt our keywords, for our preprocessor tools?"

    - "Buy new OS, plug that hack for that here?

    - "Not supported by us?"

    I do not suspect I am the only one having had enough of it all. And I hope you can see this too:

    1. GCC (for one), ready with evolution prototypes.

    2. Linux (plenty of great down to metal and great packaging as of late).

    3. Wealth of good, lightweight HTTP servers and libraries.

    All open, well-supported and running huge load tests out there.

    There should be at least be a replacement, but nah no indication of that either.

    EEvery single day I wonder why even bother with this VS and IIS  nonsense, or who makes development and business decisions over there?

    I have, sincerely, tired myself out trying to see sense in what is being done over there, but someone (plural or singular) is losing the plot.

    The products you guys make are made obsolete far quicker than adopted. Just wish I knew that before I bothered with any of the 'platforms' and 'frameworks'.

  • Great. Another library that becomes unsupported before i get the chance of even learning it. I guess it wasn't that great, anyway. ;-)

    But who needs MS libraries? I, for one, just need standards compliance (C++0x and C99).

  • If I were you guys, I would not be investing anymore time developing C++ applications on any MS platform.  The only thing they will support for a few years, is the technology used to migrate/integrate C++ code to .NET framework.  I can easily see MFC/ATL/COM having no support in a year or two.  The push is for everything sans kernel/drivers, to go .NET.

    I don't know about you guys, but we have .NET app that is terrible performance wise, and the more we optimize, the less our increase in performance gets.  I guess if performance is a main concern you should look into Linux/C++ as mentioned before.

  • Go to

    it works on all platforms....

  • I am shocked - having not suscribed to this blog I found this post just by accident. :-(

    After digging now for days through the ATL Server reference I finally thought it would be THE approach to elevate our VC8 MFC application to become a webservice (and implementing an ASP.NET based consumer working as the UI)...

    What approach would you recommend? Or in other words: which technology horse to ride now for web-enabling an unmanaged VC8 MFC application)?

  • Now ATL won't be supported any more, I wonder which technology the new VS 2008 will provide to C++ developers to write web services. Can the VS 2008 team answer my question? Thanks.

  • Hello

    From our libraries team:

    While Microsoft is actively investigating native solutions for web-service development, we are still early in this process and have nothing formal to announce at this time.  If you have an immediate need to implement web-services we recommend you wrap your native functions with managed code and use Window Communications Server (WCS) for the web-service calls.  The interop facilities of Visual C++ (including C++/CLI and the IJW technology) should simplify this work.



Page 1 of 1 (8 items)