If you’re asking if a .NET application can run 24/7 then the answer would be yes. You’d probably want it to be a service, but it’s not necessary. It depends on the purpose of the application.
Yes. Perhaps you could tell us more though, since all general purpose languages in wide use today are adapted for this use case. What in particular are you worried about?
My program would be a basic console program dealing with the cryptocurrency market. What I’m worried about is that it fails or crashes after a long time running.
Sure is.
I wrote an app once 10 or so years ago that sat in the Windows task tray that just hung out in the background waiting for a couple different events.
Because it was event-based, it used darn near 0 CPU cycles. Small memory footprint, too.
Ran for months at a time without fail. I figure it would have run for years if the machine didn’t get rebooted from time to time.
Without any more information in the post, the only answer I can really give is yes, it can be.
On which platform, and what sort of program? A web app, desktop/console app, service/daemon?
It would be a console program
Yes, I run dotnet apps for months at a time as durable functions (Which you might want to look into depending on your needs)
They run great.
C# devs
null reference exceptions