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

41–50 of 79 posts

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

#41

Post by Avalaxy »

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…

> it would leave us reliant (correct me if I'm wrong here) on a lighter weight version of VS.NET so

No, you can just use the normal Visual Studio, with ReSharper support.

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

#42

Post by Avalaxy »

cmdkeen wrote: post #31
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.

> 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?

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

#43

Post by jasonkester »

Avalaxy wrote: post #41
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…

> it would leave us reliant (correct me if I'm wrong here) on a lighter weight version of VS.NET so No, you can just use the normal Visual Studio, with ReSharper support.

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.

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

#44

Post by sundvor »

jasonkester wrote: post #43
Avalaxy wrote: post #41

Earlier quoted context omitted.

> it would leave us reliant (correct me if I'm wrong here) on a lighter weight version of VS.NET so No, you can just use the normal Visual Studio, with ReSharper support.

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.

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

#45

Post by jsingleton »

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…

I'm tracking the dependencies of libraries at: https://anclafs.com (ASP.NET Core Library and Framework Support)

Prefix is on there so I'll update it to support .NET Core in addition to the ASP.NET Core it already supported (on .NET 4.5).

Migrating anything big is probably a bad idea but for new projects Core might be a good option.

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

#46

Post by moron4hire »

eberkund wrote: post #20
cm2187 wrote: post #16

Earlier quoted context omitted.

No, my understanding of .Net core is that this is also the way they want to get back on devices. I think Xamarin will ultimately be based on .net Core. And for a mobile app, you bet you need a way to manipulate images. Even for websites, depends on what sort of websites you do, but I often need to display charts, so being able to generate images on the fly.

Why are you generating images on the fly to display a chart? Why not send the data points and render a chart clientside using JavaScript? There are plenty of libraries for that.

A lot of clients want native PDF output for their reports. None of the PDF generating libraries I know of support running JS. So if you want the same charts in both, you need to generate the images server side.

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

#47

Post by sjellis »

oblio wrote: post #34
zubspace wrote: post #27

Earlier quoted context omitted.

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

In the last presentation that I saw, the line was that Mono would continue to exist as a full .NET implementation to support Xamarin mobile apps. The reason given was that .NET Core was scoped as a run-time for server applications, so no work had been done on making it run on mobile devices, whilst Mono has been used in production on those platforms for some time.

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

#48

Post by dozzie »

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.

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

#49

Post by nikon »

cm2187 wrote: post #24

Stupid question. How do you share IPs if all the websites on a machine are running their own webserver? When running in IIS, IIS handles the virtual hosts. Unless we found a massive stach of IPv4 IPs?

nginx reverse proxy would be relatively simple.

There's even some docs straight from the asp.net site[0].

It's a bit of a paradigm shift from the "old" way but it's quite a normal thing to do with Node.js for example.

[0] - https://docs.asp.net/en/latest/publishing/linuxproduction.ht...

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

#50

Post by dodyg »

restlessmedia wrote: post #37
dodyg wrote: post #33

Earlier quoted context omitted.

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.

If you have anything particular in mind, please create an issue and I will get to them eventually.
Post reply on HN