News for hackers. Stuff that matters.

A comment on The new ASP.NET Core 2.0 packages can no longer be used on .NET Desktop.

Re:The new ASP.NET Core 2.0 packages can no longer be used o... by jug on Tuesday May 09, 2017 @03:56AM (#14298404)
I sometimes feel like I need a PhD to understand Microsoft's overarching .NET philosophy and how it all interoperates. It's strange, because the systems and what they are supposed to be able to do in terms of computing, human computer interfaces, and networking is largely unchanged since decades back. What is going on? Isn't the only major change recently that mobile devices have become more popular targets and web development is more useful due to web browsers being cross-platform renderers?
[ Parent | on HN ]
Re:The new ASP.NET Core 2.0 packages can no longer be used o... by OliverJones on Tuesday May 09, 2017 @06:52AM (#14298947)
Still better than monikers and apartment threading models.
[ Parent | on HN ]
Re:The new ASP.NET Core 2.0 packages can no longer be used o... by DanielBMarkham on Tuesday May 09, 2017 @04:49AM (#14298562)
I hear you, and I feel this pain.

I give up.

I have better things to do.

[ Parent | on HN ]
Re:The new ASP.NET Core 2.0 packages can no longer be used o... by windwake12 on Tuesday May 09, 2017 @06:14AM (#14298829)
It's incredibly frustrating. I've been on the .NET wagon since ASP.NET 1.0 (and ASP before that), and my day to day friction with .NET has been increasing steadily over the last few years as more and more of the eco system starts to support "core".

Looking over an example doc of how to host .NET in IIS (by far the most common approach) really shows how out of control it has become: https://docs.microsoft.com/en-us/aspnet/core/publishing/iis

It's a mess.

[ Parent | on HN ]
Re:The new ASP.NET Core 2.0 packages can no longer be used o... by manigandham on Tuesday May 09, 2017 @09:50AM (#14299943)
Hosting in IIS with .NET Core is no different than before, it all works the same. Only difference is that IIS won't be running the code but just acting as a simple proxy so you turn off the "Managed Code" setting in the application pool for that site. Than just web-deploy like before and everything works.

All those other settings are settings that were there before.

[ Parent | on HN ]
Re:The new ASP.NET Core 2.0 packages can no longer be used o... by tmzt on Wednesday May 10, 2017 @02:41PM (#14310528)
Does restarting the app pool reload the application? What about changing the config file?

Is IIS just configuring http.sys at this point? Are modules still invoked during the request?

[ Parent | on HN ]
Re:The new ASP.NET Core 2.0 packages can no longer be used o... by UK-AL on Tuesday May 09, 2017 @06:30AM (#14298870)
That's because it's IIS. Setting up apache is similarly difficult.

There's nothing stopping you just using self hosted websites.

[ Parent | on HN ]
Re:The new ASP.NET Core 2.0 packages can no longer be used o... by mattmanser on Tuesday May 09, 2017 @04:54AM (#14298573)
No, the major change is they're taking their windows only framework and making it cross-platform.
[ Parent | on HN ]
Re:The new ASP.NET Core 2.0 packages can no longer be used o... by flukus on Tuesday May 09, 2017 @06:44AM (#14298921)
Which involved a tonne of major, breaking changes.
[ Parent | on HN ]