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

51–60 of 79 posts

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

#51

Post by philippelh »

ofir_geller wrote: post #8

I recently built a web app with the new dotnet core . the changes were not so bad, I even found that the docs were nicer than the ones you find for the "old" asp. After having to configure camalCase for json a couple of times I like the new default. But migrating an existing app at this point is out of the question, when I no longer need to have nugget packages with rc in the version name we might do it.

If you're talking about project.json, it's already dead :/ http://xoofx.com/blog/2016/05/11/goodbye-project-json/

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

#52

Post by dan_b »

sundvor wrote: post #44
jasonkester wrote: post #43

Earlier quoted context omitted.

Glad to hear. I hadn't seen them mention it anywhere, and since it was such an obvious dealbreaker, I would have expected it to be a major talking point.

Yep, Resharper is fine but NCrunch won't work for any projects targeting Core, however.

...and that is a dealbreaker.

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

#53

Post by thomasz »

Avalaxy wrote: post #42
cmdkeen wrote: post #31

Earlier quoted context omitted.

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.

> very clear that you almost certainly shouldn't be exposing Kestrel to the internet without going through something like nginx or IIS. Why is that? Will you still have the performance benefit of Kestrel if you use IIS in front of it? How would that work?

IIS running your web app is kinda slow, because the request has to be pumped through a long, old and rusty pipeline.

IIS as a reverse proxy in front of kestrel should be very fast.

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

#54

Post by snarfy »

jasonkester wrote: post #38

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 p…

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

So why would you do it in the first place? Because "It's the Future"?

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

#55

Post by faragon »

dozzie wrote: post #48
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…

> Wasn't IIS "state of the art"? AFAIK even venerable Apache performed better than IIS, and Apache is not the fastest web server out there.

Sure, it was irony ;-)

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

#56

Post by maxxxxx »

taspeotis wrote: post #13
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.

.NET Core has neither WinForms nor WPF. It's very much focused on web applications. System.Drawing might be useful for ... one in ten? web applications. And they have released it, and it's getting plenty of traction. Take a quick scroll through here: http://referencesource.microsoft.com/#System.Drawing/commonu... To re-use System.Drawing Microsoft would need to re-implement all those methods in a cross-platform, bug-…

A lot of stuff in System.Drawing is pure algorithm and should be easy to port to other platforms. It will be tricky once you do screen output but the image processing routines shouldn't be too hard to port and they are super useful for a lot of web apps that do reporting and other things.

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

#58

Post by cmdkeen »

Hondor wrote: post #57

It's depressing to me that no talk about .Net Core even bothers to mention desktop apps. Winforms and co aren't even on the radar. I guess I'm stuck in the past.

It supports UWP development. The .Net Framework isn't going anywhere though, if you're doing Windows desktop development in a legacy framework then you don't need the cross platform-ness of Core.

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

#59

Post by avisser »

jasonkester wrote: post #38

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 p…

> on a lighter weight version of VS.NET so we'd roll back the clock about 10 years on ReSharper-like goodness.

I've been using Rider from JetBrains on and off for a few months. I'd recommend it. It's great to just remove MS from the picture and come that much closer to using IntelliJ in my Windows-based job.

Post reply on HN