Lessons Learned while Converting from ASP.NET to .NET Core
1–10 of 79 posts
Re: Lessons Learned while Converting from ASP.NET to .NET Core
#2So deploying web apps now consists of deploying a service that uses kestrel and having a reverse proxy in front of it (IIS or nginx or something)as the first point of contact.
Is that correct?
That's the recommended way to deploy?
Re: Lessons Learned while Converting from ASP.NET to .NET Core
#3So deploying web apps now consists of deploying a service that uses kestrel and having a reverse proxy in front of it (IIS or nginx or something)as the first point of contact. Is that correct? That's the recommended way to deploy?
Yes, that's correct.
I have a side project with a couple of sites on a small Linux VPS, each one runs on port 5005, 5006, 5007, and so on. nginx passes requests to each different domain name onto the servers listening on their respective ports.
Re: Lessons Learned while Converting from ASP.NET to .NET Core
#4So deploying web apps now consists of deploying a service that uses kestrel and having a reverse proxy in front of it (IIS or nginx or something)as the first point of contact. Is that correct? That's the recommended way to deploy?
Yes. If you want to see how it might work, Scott Hanselman posted an example [1] recently using nginx.
[1] http://www.hanselman.com/blog/PublishingAnASPNETCoreWebsiteT...
Re: Lessons Learned while Converting from ASP.NET to .NET Core
#5This 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.
Re: Lessons Learned while Converting from ASP.NET to .NET Core
#6What the heck are you supposed to do without System.Drawing? I find it incredible they've just plain removed it altogether.
Re: Lessons Learned while Converting from ASP.NET to .NET Core
#7What the heck are you supposed to do without System.Drawing? I find it incredible they've just plain removed it altogether.
System.Drawing is wed to GDI+ so not cross platform. There are third party libraries that work just fine.
https://github.com/imazen/Graphics-vNext
If you don't care about .NET Core but you do care about ASP.NET Core you can always run ASP.NET Core on Windows and use System.Drawing.
Re: Lessons Learned while Converting from ASP.NET to .NET Core
#8I 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.
Re: Lessons Learned while Converting from ASP.NET to .NET Core
#9What the heck are you supposed to do without System.Drawing? I find it incredible they've just plain removed it altogether.
System.Drawing is wed to GDI+ so not cross platform. There are third party libraries that work just fine. https://github.com/imazen/Graphics-vNext If you don't care about .NET Core but you do care about ASP.NET Core you can always run ASP.NET Core on Windows and use System.Drawing.
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.
Re: Lessons Learned while Converting from ASP.NET to .NET Core
#10Earlier quoted context omitted.
System.Drawing is wed to GDI+ so not cross platform. There are third party libraries that work just fine. https://github.com/imazen/Graphics-vNext If you don't care about .NET Core but you do care about ASP.NET Core you can always run ASP.NET Core on Windows and use System.Drawing.
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've been working on a solution to that. github.com/JimBobSquarePants/ImageProcessor