Recently, I have been thinking about the future of open source community projects in .NET. What causes this problem is that Microsoft is actually devouring all these projects and replacing them with their own. Each new version of the .Net framework brings not only improvements to the clr or language, but also some new features that slowly but gradually begin to replace created communities.
Just a few words:
-ASP.NET MVC - there were some ports of the Java Mvc framework, for example, for example. Maverick.Net, why didnโt they move forward, or at least left alone with slowly growing user interest.
-Entity Framework - we all know about NHibernate, but if you take a closer look at Entity Framework 4, you will see that they become similar, especially when looking at Code-First for EF
-MsSql CE 4 - Sqlite replacement
-Orchard project - replacement of DotNetNuke, N2Cms and others ...
and many others ... Now the question is: what are the consequences of this process? Do you think this can completely stop large projects / community frameworks? And then make .Net development tied only to M-things?
Iโm not very opposed, because EF + Wcf Ria + DynamicData + Data Annotations = rocks !, but doesnโt this all happen in the wrong direction?
source share