>>>>Not yet. Even if I read and play with it we are as most shops behind the curve and have to implement what was leading edge last year or so and once established in that mode we can't take time to re-write if current code works.
>>>
>>>Not only that, but what if Entity Framework goes the way of LinqToSql? It seems to be a good practice to drag your feet for a few months/years before committing to a methodology change, especially when Microsoft is involved.
>>
>>Probably true. I am feeling pretty good about C#. I'll be feeling even better when I get a job <g>.
>
>C# is good stuff. If I had any advice it would be to not drink the kool-aid that the MS evangelists are handing out. Let something prove itself over time in a real-world situation. At least let it get to SP1, and that oftentimes even SP1 isn't enough (See Visual Studio 2008).

I really like it. Some languages resonate, some don't. C# does. Its austerity appeals to me, along with being part of a powerful framework that makes life easier.