4 ms·

Announcing the Fastest ASP.NET Yet, ASP.NET Core 1.1 RTM

64 points by benaadams 10y ago

DenisM 10y ago
Anyone migrated from ASP.NET MVC 4 to Core yet? Is that a lot of hassle?
- roryisok 10y ago
  I've come up against one hurdle, which is that the entity framework stuff is configured very differently to what I'm used to. Seems to want to force me to go code first. Admittedly I've only dabbled in it.
  - nightski 10y ago
    Yea I'd switch today except that EF Core is missing a lot of functionality. It's unfortunate. If I was writing from scracth I could probably work around the limitations to an extent. But porting a large application wouldn't be worth it.
- kierenj 10y ago
  I imagine migrating will be, but re-writing is really refreshing. The API is great fun to work with, extend, and understand. The other poster is right about EF Core, while it's come on leaps and bounds, it's a very different product, and unfortunately (likely just my model), still oodles of issues. But it won't stop me using it - again, far superior product IMO. The MS team on GitHub are fantastically helpful, too.
  - DenisM 10y ago
    I'm still on LINQ2SQL, never got the chance to move to EF :)
skyde 10y ago
Could someone explain why "ASP.NET Core 1.1" Kestrel webserver decided to use LibUV DllImpor [1] instead of .NET Asynchronous Server Socket (System.Net.Sockets) [2]. Does that mean that the managed implementation of Async socket is broken and was too slow? [1] "https://github.com/aspnet/KestrelHttpServer/blob/dev/src/Microsoft.AspNetCore.Server.Kestrel/Internal/Networking/Libuv.cs" https://github.com/aspnet/KestrelHttpServer/blob/dev/src/Mic... [2] https://msdn.microsoft.com/en-us/library/bew39x2a(v=vs.110).aspx https://msdn.microsoft.com/en-us/library/bew39x2a(v=vs.110)....
- davidfowl 10y ago
  Timing. When we started ASP.NET cross platform there were not cross platform sockets. That came much later. We'll likely move back to sockets in the future (we're actively looking at this).
ksec 10y ago
What i wonder if how much will this make Stack Overflow faster, it is already VERY fast with no cache. https://news.ycombinator.com/item?id=12790650 https://news.ycombinator.com/item?id=12790650

64 points by benaadams 10y ago

DenisM 10y ago

Anyone migrated from ASP.NET MVC 4 to Core yet? Is that a lot of hassle?

roryisok 10y ago
I've come up against one hurdle, which is that the entity framework stuff is configured very differently to what I'm used to. Seems to want to force me to go code first. Admittedly I've only dabbled in it.
- nightski 10y ago
  Yea I'd switch today except that EF Core is missing a lot of functionality. It's unfortunate. If I was writing from scracth I could probably work around the limitations to an extent. But porting a large application wouldn't be worth it.
kierenj 10y ago
I imagine migrating will be, but re-writing is really refreshing. The API is great fun to work with, extend, and understand. The other poster is right about EF Core, while it's come on leaps and bounds, it's a very different product, and unfortunately (likely just my model), still oodles of issues. But it won't stop me using it - again, far superior product IMO. The MS team on GitHub are fantastically helpful, too.
- DenisM 10y ago
  I'm still on LINQ2SQL, never got the chance to move to EF :)

skyde 10y ago

Could someone explain why "ASP.NET Core 1.1" Kestrel webserver decided to use LibUV DllImpor [1] instead of .NET Asynchronous Server Socket (System.Net.Sockets) [2]. Does that mean that the managed implementation of Async socket is broken and was too slow? [1] "https://github.com/aspnet/KestrelHttpServer/blob/dev/src/Microsoft.AspNetCore.Server.Kestrel/Internal/Networking/Libuv.cs" https://github.com/aspnet/KestrelHttpServer/blob/dev/src/Mic... [2] https://msdn.microsoft.com/en-us/library/bew39x2a(v=vs.110).aspx https://msdn.microsoft.com/en-us/library/bew39x2a(v=vs.110)....

davidfowl 10y ago
Timing. When we started ASP.NET cross platform there were not cross platform sockets. That came much later. We'll likely move back to sockets in the future (we're actively looking at this).

ksec 10y ago

What i wonder if how much will this make Stack Overflow faster, it is already VERY fast with no cache. https://news.ycombinator.com/item?id=12790650 https://news.ycombinator.com/item?id=12790650