This blog is about developing Windows applications using Visual Studio. All postings on this weblog are provided "AS IS" with no warranties, and confer no rights. Use of any samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
Your host Nikola Dudar is a Program Manager in Windows division of Microsoft Corporation. He has been working on Windows Web Services API during Windows 7 and various additions to Visual C++ during VS2005 and VS2008. More details are in LinkedIn profile under Nikola's formal name Mykola Dudar.
If you are interested in program management and project management, check out my other blog at http://www.pmsnack.com/ where I collect best practices and other topics interesting to program and project managers.
To send feedback, comments or requests for new posts, please use the contact form.
Well, finally I have a good news. We have started working on preparing STL/CLR (former called STL.NET) for the next Community Technology Preview of the Orcas-version of Visual Studio. We are targeting CTP#2 that is planned to be released in late July/early August timeframe. We are going to show a build of STL/CLR which we are currently using for all investigations and changes planning. By the time it is available in CTP, we are expecting to have investigated all major issues in the current design and implementation. I am planning to share with you a list of “known issues” published on either a blog (mine or VC) or in readme. I may be asking for input on a design in some specific areas and more hign level feedback on overall design/usability/goodness. As you may see I have opened a new category on my blog in which I am going to try hard to regularly make posts about STL/CLR try to prepare as much of background information about the library as possible.
With this said, I will be moving to another post to discuss question that I really want to answered today. The question of what is STL/CLR and for who it is intended for.