← Back to context Comment by croes 9 days ago .NET versions are faster outdated then .Net Framework 4.8 6 comments croes Reply 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. croes 9 days ago 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. tgtweak 9 days ago You're talking about .net for server applications right? The discussion above is for client apps being distributed for windows endusers. rblatz 9 days ago Just ship a self contained build? 1 reply → stackskipton 9 days ago We have a small MAUI part of the application, it's not massive but it's working fine with .Net Upgrades.
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. croes 9 days ago 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. tgtweak 9 days ago You're talking about .net for server applications right? The discussion above is for client apps being distributed for windows endusers. rblatz 9 days ago Just ship a self contained build? 1 reply → stackskipton 9 days ago We have a small MAUI part of the application, it's not massive but it's working fine with .Net Upgrades.
croes 9 days ago 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.
tgtweak 9 days ago You're talking about .net for server applications right? The discussion above is for client apps being distributed for windows endusers. rblatz 9 days ago Just ship a self contained build? 1 reply → stackskipton 9 days ago We have a small MAUI part of the application, it's not massive but it's working fine with .Net Upgrades.
stackskipton 9 days ago We have a small MAUI part of the application, it's not massive but it's working fine with .Net Upgrades.
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?
1 reply →
We have a small MAUI part of the application, it's not massive but it's working fine with .Net Upgrades.