3 ms·
I've found upgrade hell can apply to C#/dotnet stuff too. I work on a project that has attempted to upgrade Entity framework versions multiple times and keeps p
by manifestsilence 10y ago
I've found upgrade hell can apply to C#/dotnet stuff too. I work on a project that has attempted to upgrade Entity framework versions multiple times and keeps pushing it off because we get buried in compile time errors. It's a case where Microsoft supported several different paths to architect an app and then quietly deprecated half of them - database first vs. code first, POCOs vs. ObjectContext, etc. and we happened to be on the losing side of history. Compile-time errors are definitely easier to find, but the path to fixing them can be just as bad. What I really long for is good documentation and a clear path forward for each breaking change.
- douche 10y agoNever much liked EF... Linq-to-SQL may be dead/stable, but we're still using it, and it's pretty slick - course it is only for SQL server.
- ktRolster 10y agoIndeed, Microsoft's lack of commitment to APIs is what inspired Joel's famous essay: http://www.joelonsoftware.com/articles/APIWar.html http://www.joelonsoftware.com/articles/APIWar.html IMHO .net has lost some stability with the recent packaging systems like NuGet and chocolatey; they don't really encourage stability.
- DonnyV 10y agoThe problem is not C# or .NET. The issue is Entity framework. Either stop being scared of using SQL and use something like PetaPoco or stop trying to turn objects into records and use Mongodb and just store the damn objects.