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.
Sorry, I know I promised more information about STL/CLR and did not keep my promise last two days. It is just I have a portion of my time dedicated to emails from you or posts made by you on forums or in newsgroups. In particular last two days I have spent that portion of time on either discussing posts on CodeGuru slow chat on VC++ past, current and future or replying to these posts. I am inviting you to participate in discussion on this forum if you have done so already.
However there are two questions that I have been asked about STL/CLR that I would like to quickly answer.
a) Will STL/CLR containers support storing object of native types (ClassA*, for example)?
The answer is not, we are not going to support this scenario. We expect developer to use STL.
b) Is iostream part of Standard C++ library is part of STL/CLR?
Again answer is no, stream support is not part of STL/CLR. We expect you to either use stream support provided by CLR or SCL iostreams after data is marshaled from managed types to native types.
This is all for today.