Is .NET 4.0 just a show?
- by Will Marcouiller
I went to a presentation about the .NET Framework and Visual Studio 2010, last night. The topis were:
ASP.NET 4 - Some of the new features of ASP.NET 4
More control over ClientID's in WebForms;
Output Caching;
... // Some other stuff I don't really remember being more in framework and WinForms world.
Entity Framework 2.0 (.NET 4.0)
T4 Templates;
Domain driven development;
Data driven development;
Contexts (edmx files);
Some of real-world limitations of EF4 (projects with over 70 to 75 tables);
Better POCO support, despite there are still these hidden EntityObject and StructuralObject, but used differently in comparison to EF 1.0 so that it doesn't take off your inheritance;
Allows to easily choose how to persist the hierarchy into the underlying database;
Code only (start working with EF4 directly from your code!);
Design by Contract (DbC).
The most interesting feature is, and only, as far as I'm concerned, all related to parallelism made easier. Which really works! No additional assembly references to add.
In conclusion, I'm far from impressed about .NET Framework 4.0, apart that it makes some things easier to do. But when you're used to make it a way, it doesn't really change much, in my opinion.
Is it me who cannot foresee what .NET 4.0 has to offer?
What would you guys base your decision on to migrate to .NET 4.0, in a practical way?
