zombie

I think the point I was trying to make is that I would like to use common library type functions suchas strings, containers and iterators from the .NET framework, and these classes should be optimised for performance. To be honest, in the future, I don't really want to see multiple libraries from Microsoft with overlapping functionality. But thats just my 10 cents.

In the past the STL implementation and in fact the template implementation in Microsoft C++ was quite poor. Just resolving compile errors was a pain,intellisense was useless and debugging a nightmare. So you might understand why I am scheptical about use of templates.

Thanks for the links and insight.

I am surprised that you will have templates and generics. I have used the STL because it was supported on a lot of compilers for different platforms, it performs well, however, I have always disliked the interfaces. Are you including this so that you can port existing code that uses the STL and templates?

I can't imagine writing any new managed code using STL or templates unless I had a good reason.

I like the idea of seperating object persistence from object programming. Have you considered using attributes to define the object / database mapping in a similar way to XML serialization?