Comment by stackskipton
9 days ago
Point? I’m SRE on .Net project, we have been through 6-8-10 and its cost us about 2ish hours of work each time. As long as you don’t get crazy, .Net upgrades is just matter of new SDK and runtime and away you go.
9 days ago
Point? I’m SRE on .Net project, we have been through 6-8-10 and its cost us about 2ish hours of work each time. As long as you don’t get crazy, .Net upgrades is just matter of new SDK and runtime and away you go.
A .net framework 4.8 app has zero hours of work.
Why is it ok that you have to invest 2 times number of apps hours just because MS has such a short life cycle for its .NET versions.
You're talking about .net for server applications right? The discussion above is for client apps being distributed for windows endusers.
Just ship a self contained build?
This was a sidecar application distributed by literally millions of installs per day - so having a 25MB "self contained" build was out of the question - we were targeting KB-sized distributables not 10's of MB.
We have a small MAUI part of the application, it's not massive but it's working fine with .Net Upgrades.