Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Lessons Learned while Converting from ASP.NET to .NET Core

stackify.com

Post reply on HN
Print view View original

31–40 of 79 posts

Re: Lessons Learned while Converting from ASP.NET to .NET Core

#31

Post by cmdkeen »

faragon wrote: post #29

"As part of .NET Core, Microsoft (and the community) has created a whole new web server called Kestrel. The goal behind it has been to make it as lean, mean, and fast as possible. IIS is awesome but comes with a very dated pipeline model and carries a lot of bloat and weight with it. In some benchmarks, I have seen Kestrel handle up to 20x more requests per second. Yowzers!" So the new Microsoft web server replacing…

It isn't replacing IIS, and they're very clear that you almost certainly shouldn't be exposing Kestrel to the internet without going through something like nginx or IIS.

Kestrel does the bare basics of a web server, it goes a little bit further than the dev servers built into plenty of other language's web frameworks.

Re: Lessons Learned while Converting from ASP.NET to .NET Core

#32

Post by chrisherring »

eksemplar wrote: post #5

This is quite frankly an excellent list of why we won't be changing any time soon, with key points being: > Things like virtual hosts, logging, security, etc. > Newtonsoft now defaults to camelCase > Log4net doesn’t work and neither do countless other dependencies, unless you target .NET 4.5 I mean a lot of those things are the reason we're using .Net over more other technologies to begin with.

.net core certainly does have security, logging etc. IIS, as opposed to kestral, has more features and you can host under IIS so this is a non issue.

The camelCase setting is a one line code change if you don't like it. Not at all a reason to avoid the framework. It's using newtonsoft for this so it may even be a change in the package itself? Anyway I changed the default and then ended up reverting back anyway since camelCase is a better format when using the objects in JavaScript.

It's not meant to support everything as the goal is cross platform. IMO it's a great platform if you understand its limits.

Re: Lessons Learned while Converting from ASP.NET to .NET Core

#33

Post by dodyg »

eksemplar wrote: post #5

This is quite frankly an excellent list of why we won't be changing any time soon, with key points being: > Things like virtual hosts, logging, security, etc. > Newtonsoft now defaults to camelCase > Log4net doesn’t work and neither do countless other dependencies, unless you target .NET 4.5 I mean a lot of those things are the reason we're using .Net over more other technologies to begin with.

aspnet.core works fine with .NET 4.5.

For me the big attraction to aspnetcore is not the aspnetcore MVC, but the new infrastructure that they build around it. I am working on a project right now going down to every single little tiny details of aspnetcore capabilities https://github.com/dodyg/practical-aspnetcore

Re: Lessons Learned while Converting from ASP.NET to .NET Core

#34

Post by oblio »

zubspace wrote: post #27
blakeyrat wrote: post #9

Earlier quoted context omitted.

It's only "wed to GDI+" because the current implementation is. Nothing's preventing them from implementing a cross-platform System.Drawing. There's no magic involved in what it does that requires GDI+. I find it unbelievable that they would even consider releasing this without System.Drawing or equivalent being available.

I'm confused. Didn't Microsoft purchase Xamarin lately? There's http://www.mono-project.com/docs/gui/drawing/ and https://github.com/mono/mono/tree/master/mcs/class/System.Dr... all waiting to be integrated. But I guess, this won't happen. So many people would embrace a truly cross platform framework will all bells and whistles. But instead we have this disturbing split between .NET, .NET Core and Mono.

.NET Core is slowly reimplementing/integrating all truly cross platform .NET classic APIs (https://github.com/dotnet/core/blob/master/roadmap.md). My guess is that at this point they didn't have the bandwidth to include what you're talking about in the first version but they will include it later on.

Long term Mono is probably just going to become a sort of .NET "distribution" on top of .NET Core, it will include things which Microsoft deprecated such as Winform. And it will probably be not maintained at the same level .NET Core itself is. I don't think there will be any reason to use Mono in the future, except for legacy Mono apps...

Re: Lessons Learned while Converting from ASP.NET to .NET Core

#36

Post by ygra »

cm2187 wrote: post #23
nikbackm wrote: post #21

Earlier quoted context omitted.

> generate images on the fly Isn't SVG or canvas more suitable for that on the web?

If you want to draw the chart from scratch perhaps but I use a library to generate the chart then send it as an image to the client. Very few lines of code required in .net, no javascript required.

You don't need JS to generate SVG server-side either ...

Re: Lessons Learned while Converting from ASP.NET to .NET Core

#37

Post by restlessmedia »

dodyg wrote: post #33
eksemplar wrote: post #5

This is quite frankly an excellent list of why we won't be changing any time soon, with key points being: > Things like virtual hosts, logging, security, etc. > Newtonsoft now defaults to camelCase > Log4net doesn’t work and neither do countless other dependencies, unless you target .NET 4.5 I mean a lot of those things are the reason we're using .Net over more other technologies to begin with.

aspnet.core works fine with .NET 4.5. For me the big attraction to aspnetcore is not the aspnetcore MVC, but the new infrastructure that they build around it. I am working on a project right now going down to every single little tiny details of aspnetcore capabilities https://github.com/dodyg/practical-aspnetcore

Some good work there, I'd be interested to see more examples of aspnetcore recipes.

Re: Lessons Learned while Converting from ASP.NET to .NET Core

#38

Post by jasonkester »

Just from the examples on this list, it sounds like the only winning move is not to play.

I have a handful of sites running ASP.NET 4.5. Migrating them would cost an unknown amount of time and require substantial rewriting of major components (such as all data access). It might not even be physically possible to do, given dependencies on libraries that are still 4.5 only.

It sounds like it would also kill our build process dead (adding another major rewrite to the tally). And of course, it would leave us reliant (correct me if I'm wrong here) on a lighter weight version of VS.NET so we'd roll back the clock about 10 years on ReSharper-like goodness.

As reward for this, migrating over to Core would gain me roughly $0 in business value.

The alternate course is to stay with 4.5 for as long as possible, eventually moving across when Microsoft decide to VB6 it.

Sounds like a plan.

Re: Lessons Learned while Converting from ASP.NET to .NET Core

#39

Post by cm2187 »

35bge57dtjku wrote: post #30
cm2187 wrote: post #28

Earlier quoted context omitted.

So you set up the self hosted webservers on some non routable local IPs / ports, and set up IIS to map these IPs / ports to the external IP / hostname? Sounds complicated. You have two states to maintain and keep synced. The .net core servers and IIS.

Of course it's complicated, you stipulated that all websites are running their own web server.

I am not. This seems to be what .net core does, according to the article.
Post reply on HN