Hacker News Reader

Comment by revskill | Hacker News Reader

Installing .NET stacks including Runtime, SQL Server is a nightmare to me. When an error occurs during installation process, you got stuck , hopeless and depressed. Hey MS, fix your installation process first.

View on HN

The build scripts (for coreclr, corehost, corefx) are a mess. I worked on getting the build working for Yocto, and there were so many things done differently all over the place. They need a single team to go through their entire build process, top-to-bottom.

Don't get me wrong though, I worked to integrate it into Yocto because I love .NET/C#, but the build system needs a lot of love.

I don't know if it solves your specific scenario, but I do know that there's been some work done in this area.

See https://github.com/dotnet/source-build#net-core-build-script... and https://github.com/dotnet/arcade#arcade

Did you try SQL Server in a container? It's way more easy to get up and running than installing it on Windows.

https://hub.docker.com/r/microsoft/mssql-server

No, docker is a cancer to me, Docker has the same problem with installation on Windows now. SO if i use Docker to install MS stack, i have two problems now.

.NET Desktop/Full Framework’s been fine after some initial missteps when they first bundled it in the OS with Vista.

.NET Core has self contained deployments so you can bundle it with your app in a .zip.

For development or continuous integration SQL Server comes in a container now.

> .NET Desktop/Full Framework’s been fine after some initial missteps when they first bundled it in the OS with Vista

They first bundled (1.0) with xp, and every OS since. I don't know why they bothered considering practically every app has had to bundle newer versions with the installer. They could have at least pushed newer versions with windows update.

It was so absurd that only a windiv power play against devdiv can adequately explain it.

Never heard about this kind of issues, can you share specific ones you had?

seconded. I've never had an installation fail, but I have always installed on windows. I'm curious if its due to installing on other OS's that aren't supported as well, as I am looking to jump stacks and thought .net core would have been a hassle free transition to a new OS at least

installing .net core on linux is easier than on windows (they create native linux packages, so apt install ... or yum install is enough or docker, whatever they provides so much these days), and macos provides a pkg file, which is just click trough.

Always been piss easy for me, and I've done it for years now.

What platform/OS? Are you installing from a package manager, from binary, or from source?

I used Windows before.

You can run Postgres with .NET these days no problem.

http://www.npgsql.org/efcore/

Where are you getting stuck? What errors?

I don't remember because i don't use MS stack anymore for a long time. Just an alert to fix past issues for everyone that needs it.

How is an issue you had a long time ago relevant now? And why do you say "fix X first" if you don't even know whether it's still a problem?

Reply on news.ycombinator.com