Hacker News Reader

Comment by bob1029 | Hacker News Reader

I think we need to be super precise when we use the word "managed". Today, we use EC2/Azure VMs to run a lot of .NET 6+ apps. I consider these to be managed resources. My involvement with those servers is an email from the hypervisor ~once a year politely requesting a reboot.

I don't think .NET has any specific implications regarding where the product is hosted. If you are referring to the Microsoft insight/Azure integration crap, we use 0% of that.

View on HN

That's basically what I mean. I just want to deploy the app and not have to worry about anything OS-related, including IIS config, SSL, etc.

That's exactly what I do - I build a monolith using the self-contained deployment feature and zip it up to the server to run.

The management of certificates, configuration, etc. is built directly into any product I work on. Outsourcing this stuff to IIS, et. al. is exactly how you wind up hating all of this tech in the first place.

Prerequisites are zero if you do this right. I can take a blank EC2 server, copy the binaries over and run them immediately. I don't even have to install any runtimes or SDKs.

How do you setup your webserver. This is the most challenging part for me.

Here's my process. Build locally, publish, upload to server, dotnet run... Now what?

Modern .NET contains the web server. It's not an external thing anymore. You include a .NET library to host your stuff. Check out the minimal api reference:

https://learn.microsoft.com/en-us/aspnet/core/fundamentals/s...

https://learn.microsoft.com/en-us/aspnet/core/fundamentals/m...

Literally everything runs inside your process now, including the database if you go for SQLite.

C# is heavily influenced by golang now. Run with 0 dependencies. Web server bundled.

> C# is heavily influenced by golang now

Source ?

Reply on news.ycombinator.com