News for hackers. Stuff that matters.

A comment on Lessons Learned while Converting from ASP.NET to .NET Core.

Re:Lessons Learned while Converting from ASP.NET to .NET Core by eksemplar on Tuesday September 06, 2016 @12:20AM (#12433643)
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.

[ Parent | on HN ]
Re:Lessons Learned while Converting from ASP.NET to .NET Core by dodyg on Tuesday September 06, 2016 @04:56AM (#12434497)
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

[ Parent | on HN ]
Re:Lessons Learned while Converting from ASP.NET to .NET Core by restlessmedia on Tuesday September 06, 2016 @05:15AM (#12434580)
Some good work there, I'd be interested to see more examples of aspnetcore recipes.
[ Parent | on HN ]
Re:Lessons Learned while Converting from ASP.NET to .NET Core by dodyg on Tuesday September 06, 2016 @08:22AM (#12435406)
If you have anything particular in mind, please create an issue and I will get to them eventually.
[ Parent | on HN ]
Re:Lessons Learned while Converting from ASP.NET to .NET Core by chrisherring on Tuesday September 06, 2016 @04:55AM (#12434491)
.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.

[ Parent | on HN ]