service-fabric
service-fabric copied to clipboard
microsoft
Public service announcement to the Service Fabric team
Just in the Service Fabric team is not aware, Microsoft intends to release a version 7 of .NET. What this means is that you should probably start testing your code NOW, so that when version 7 does ship, you won't be caught completely flat footed like you were with version 6.
Is there an official statement on net6.0 compatibility yet? Why do I ask?
Well if one looks here...
https://github.com/microsoft/service-fabric/issues/1292#issuecomment-1009472883
It would appear net6.0 isn't officially supported. But if you look here...
https://github.com/microsoft/service-fabric/blob/master/release_notes/Service_Fabric_ReleaseNotes_82CU1.md
It would appear that you do support net6.0.
So which is it? I mean you've only had SINCE NOVEMBER to come up with an answer.
Additionally .NET 7 won't be a LTS release. If support for it is delayed by months, the supported lifespan for developers will be close to none. So I hope there will be a plan in place to support .NET 7 development from the day it launches. I think the .NET 5 had similar issue that it was not LTS release and the support for it came very late in SF (August 2021), just few months before .NET 6 release.
Would love to see the modern .NET get all the love it deserves.
ASF Linux doesn't even have .NET 5 support yet let alone .NET 6, the service fabric team move at a snails pace and don't know how to do open source properly nor are they able to provide a public roadmap. We are considering moving to Kubernetes as it's just so painful waiting for basic features.
Their roadmap is a bunch of version numbers and dates, but no information on what is expected in those versions, what is the point?
They've take disengagement to an entirely new level. No responses to any of the messages here for months on end. Looks like they've even given up on the monthly conference calls (to be fair in comparison to other more effective communication avenues, they were a complete waste of time.)
We shouldn't be too hard on them though. It's not their fault, Azure really is strapped for cash.
I do question whether anyone is actually listening to this post.
SF 8.2 refreshes have been rolling out, GitHub states SF 9.0 planned for March (this month) but still no feedback on .NET 6 support from the Azure Service Fabric team. It would be great to understand who the Program Manager is for the team to understand why this information is not available or even being commented on.
This is very similar questioning to my question in November https://docs.microsoft.com/en-us/answers/questions/636450/service-fabric-net-6-support.html?childToView=746157#comment-746157
This was actually more of a test to confirm the internal rumors that Service Fabric is going the Silverlight route. I believe the PMs have already been re-assigned, no loss as they were absolutely useless. At this point I've proven over and over that the only way that you get the team's attention is to flame them on twitter with a link to your issue here. Of course, apparently I'm the bad guy for expecting accountability and for people to do their jobs.
Seriously, no one has EVER responded anywhere you might reasonably expect whether SF officially does or does not support .NET 6. That's ******* inexcusable. So I'll repeat what I've been saying for years, someone ought to be fired.
There's not much point in looking at their release schedule as they don't actually explain what's coming with each release on any roadmap. Just a version bump so it's basically a meaningless metric.
Hallelujah!!
https://techcommunity.microsoft.com/t5/azure-service-fabric-blog/azure-service-fabric-9-0-release/ba-p/3299108
Finally, luckily its a pretty good update, just a pity they don't act like the asp.net core team customer engagement wise.
