4 ms·

> If you are running .NET 8 or later install the .NET update from Microsoft Update, then restart your application or reboot the machine. This is why I advocate

> If you are running .NET 8 or later install the .NET update from Microsoft Update, then restart your application or reboot the machine. This is why I advocate for .NET in serious business contexts. You often don't have to rebuild or redeploy your software if you are using the included batteries as intended. A devops intern could handle this fix. Contrast with virtually any other ecosystem.

BartjeD 1y ago
Yes agreed, applying updates is very easy and pain free these days.
philipwhiuk 1y ago
No different to using RHEL OpenJDK on Linux and running `dnf update`
wcoenen 1y ago
This only works when deploying the application as framework-dependent, right? I think applications that use self-contained deployment still need to be rebuilt (after updating dev tools) and redeployed.
- LikesPwsh 1y ago
  Yes
pier25 1y ago
Who doesn't use containers these days to deploy web apps?
- qingcharles 1y ago
  I bare metal everything.
  - pier25 1y ago
    As do I but still use containers with dokku.
- sebazzz 1y ago
  Those outside your bubble.
sofixa 1y ago
> You often don't have to rebuild or redeploy your software if you are using the included batteries as intended Instead, your software's lifecycle is entirely dependent on the OS' lifecycle. That seems worse. And for what it's worth, it would be exactly the same with any "interpreted"/VM-based language - Java and family friends, Python, Ruby, etc. Just update the VM/interpreter and restart (the service though, not the whole server). It's for compiled languages like Go or C/C++ or Rust that you would need to recompile. I prefer it because it ensures the lifecycle only depends on you and you aren't bound by OS versions and OS updates to be able to update/downgrade library/framework/language versions.
- daveoc64 1y ago
  >Instead, your software's lifecycle is entirely dependent on the OS' lifecycle. That seems worse. It's not. .NET updates are shipped with Windows Update, but can be installed separately. Obviously for macOS and Linux you can't get them through Windows Update anyway.

BartjeD 1y ago

Yes agreed, applying updates is very easy and pain free these days.

philipwhiuk 1y ago

No different to using RHEL OpenJDK on Linux and running `dnf update`

wcoenen 1y ago

This only works when deploying the application as framework-dependent, right? I think applications that use self-contained deployment still need to be rebuilt (after updating dev tools) and redeployed.

LikesPwsh 1y ago
Yes

pier25 1y ago

Who doesn't use containers these days to deploy web apps?

qingcharles 1y ago
I bare metal everything.
- pier25 1y ago
  As do I but still use containers with dokku.
sebazzz 1y ago
Those outside your bubble.

sofixa 1y ago

> You often don't have to rebuild or redeploy your software if you are using the included batteries as intended Instead, your software's lifecycle is entirely dependent on the OS' lifecycle. That seems worse. And for what it's worth, it would be exactly the same with any "interpreted"/VM-based language - Java and family friends, Python, Ruby, etc. Just update the VM/interpreter and restart (the service though, not the whole server). It's for compiled languages like Go or C/C++ or Rust that you would need to recompile. I prefer it because it ensures the lifecycle only depends on you and you aren't bound by OS versions and OS updates to be able to update/downgrade library/framework/language versions.

daveoc64 1y ago
>Instead, your software's lifecycle is entirely dependent on the OS' lifecycle. That seems worse. It's not. .NET updates are shipped with Windows Update, but can be installed separately. Obviously for macOS and Linux you can't get them through Windows Update anyway.