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.
The first public release of STL/CLR in Orcas is available for download. This version of STL/CLR has most of core functionality done and ready to use. We are continue working on fixing code defects, adding parts of library related to interop with .Net Collection classes and tuning performance. I have posted a brief outline of know issues in this drop on VCBlog. You may find it here: http://blogs.msdn.com/vcblog/archive/2006/09/30/777835.aspx
To download September CTP to Orcas, you need to go here:
http://www.microsoft.com/downloads/details.aspx?FamilyID=82243606-d16d-445c-8949-9ee8c10cda2e%26DisplayLang=en
I would like to bring to your attention a list of feature areas in the library about which we would really like to hear your feedback (copy&paste from Post on VCBlog):
Please feel free to submit any feedback on the STL/CLR library using the Connect website, http://connect.microsoft.com/VisualStudio/. You can also leave comments on the blog. Overall, please try using STL/CLR in your everyday programming in managed code. We would specifically like to hear your feedback in the following areas:
- Usability of STL/CLR compared to STL. We would like to hear from you about what you like or don't like about using STL/CLR compared to using STL.
- Interoperability with managed code written using .Net classes in either C++ or C# or any other .Net language.
- Any missing functionality that you would expect to be in STL/CLR.
- Any performance issues you see with your application that uses STL/CLR.
Please give it a try and let us know what works and what does not work for you. I would be happy to address any concern and consider all your suggestions to improve desing and implementation of the library.
Could you please provide the STL/CLR specification in another document format as xps (e.g. as pdf)?
Thanks
Richard Kaiser
Hi Richard,
The format of the specification is one for all specs. They all start as MS Word documents and published through a centralized mechanizm. I cannot change the format.
Cheers,
Nikola
If VS2007 is the only channel for STL/CLR distribution, then what are the licensing terms for redistributing STL/CLR assemblies? I suppose if I write code that uses STL/CLR, I'll need to redistribute some STL/CLR assemblies. To do that, I need to concern myself with the licensing terms.
I really want to try out STL/CLR. But downloading the 3 something gigabytes CTP takes a long time. It would be nice if STL/CLR can be separated out and released.
The current plan for the STL/CLR assembly is that it is going to be part of .Net Framework. As long as you have installed .Net Framework, you should be able to use STL/CLR.