.NET Core 3.0 Concludes the .NET Framework API Porting Project

Re:.NET Core 3.0 Concludes the .NET Framework API Porting Pr... by tonyedgecombe on Tuesday October 15, 2019 @04:07AM (#21256450)

I keep coming back for a look every time there is a major release but it always seems quite cumbersome to me despite the fact I work in C# everyday. I ran through the Razor pages tutorial yesterday and I was surprised how heavy it all felt, I was expecting something like Flask or Sinatra.

I'm a big fan of IDEs, I couldn't imagine using C# without one.

[ Parent | on HN ]

Re:.NET Core 3.0 Concludes the .NET Framework API Porting Pr... by thrower123 on Tuesday October 15, 2019 @10:05AM (#21258442)

I've been quite happy using Nancy for the past several years. At the time we made the switch, it wasn't possible to use WebApi or MVC in a self-hosted OWIN web server, and our application had lifecycle constraints that made trying to run it out of IIS impractical.

But I've come to really like the way Nancy has explicit API routes, compared to the implicit conventional style, or slapping attributes all over everything. You can avoid a lot of the magical action-at-a-distance middleware behavior that seems to be increasingly common as well.

[ Parent | on HN ]