3 ms·

ASP.NET Core + Angular probably

• thom 9y ago
  I'd love to be able to recommend ASP.NET Core, but there have just been too many changes and U-turns. I have spent too many hours shaving the yaks of changing project formats, features missing from the old ASP.NET stack, warring dependencies, and half-finished implementations of related projects like Entity Framework Core. I _do_ believe they'll get there, but it's been painful maintaining apps built with these technologies over the past couple of years.
  • avtar 9y ago
    Which issues did you run into with EF Core? I've been dipping my toes in the water and was on the fence about investing time in their offering after seeing their long-ish roadmap or just switching to Dapper.
    • thom 9y ago
      My knowledge of the state of the art in *Core is likely out of date, partly because I have stopped trying to keep up. But last I checked, lazy loading wasn't supported, it lacked a find-by-pk method, seemingly with the knock-on effect that it didn't have any sort of identity map or anything resembling real object-graph management. I have live apps running on it, it's mostly fine, but the overriding sense I have of this stuff since the great open sourcing is of barely contained chaos. Starting from scratch today, the feeling might be different, I don't know.
  • staticelf 9y ago
    I come from a javascript world so changes are the default for me. Kidding aside, I haven't really felt any pain except some small issues but I started using it in RC already.