It will do what you want in version 3.0...
But feel free to start using it now. Adi's post is bringing back memories from conversion long gone:
I had practically this statement thrown at me about 8-10 months ago, talking about why the customer wanted to use DLinq instead of NHibernate.
Adi, my response to that is, "So?"
I can get a bottle of wine that will taste real good in 15 years, that doesn't mean that I need to start drinking it now. Sour grapes indeed.
Just to point out, another company did, Sun & Java. As for why I am using C#, have you looked at the alternatives? Before I did C# I was a C++ programmer. Can you imagine the stuff that I did with templates? I jumped into C# the moment I realize that I don't have to manage my own memory anymore. Hell, C# has one feature that is a killer. Stacktraces for exceptions. C++ has 0x324ABCD memory could not be "read".
I am not sure why, but I never got around to doing the other stuff (Java, Python, etc)...
Oh, and what is it with the babe?

Comments
Comment preview