%3CLINGO-SUB%20id%3D%22lingo-sub-1877751%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20Service%20Fabric%207.2%20Second%20Refresh%20Release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1877751%22%20slang%3D%22en-US%22%3E%3CP%3EOk%20guys%2C%20you%20REALLY%20REALLY%20need%20to%20get%20your%20acts%20together.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20it's%20readily%20apparent%20that%20you%20messed%20up%20with%26nbsp%3B%3CSPAN%3E7.2.413.9590%2C%20not%20great%2C%20but%20not%20the%20end%20of%20the%20world.%20Someone%20NEEDS%20to%20update%20the%20Service%20Fabric%20release%20schedule%20here...%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FMicrosoft%2Fservice-fabric%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2FMicrosoft%2Fservice-fabric%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIt%20still%20has%20September%202020%20as%20the%20release%20date%20for%207.2.%20I%20just%20read%20the%20above%20release%20notes%2C%20and%20it%20states%20no%20support%20for%20.NET5%20until%20v8.%20When%20can%20we%20expect%20v8%20to%20be%20available%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1878674%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20Service%20Fabric%207.2%20Second%20Refresh%20Release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1878674%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F469811%22%20target%3D%22_blank%22%3E%40AdmiralBond%3C%2FA%3E%26nbsp%3Bwe%20expect%20to%20release%208.0%20in%20the%20spring%20of%202021.%20We%20are%20currently%20targeting%20March.%20I%20have%20gone%20ahead%20and%20updated%20the%20roadmap%20to%20better%20reflect%20our%20upcoming%20timelines.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1878839%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20Service%20Fabric%207.2%20Second%20Refresh%20Release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1878839%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20we%20get%20clarification%20on%20.NET5%20compatibility%3F%20The%20release%20notes%20state%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22.NET%205%20apps%20are%20currently%20not%20supported%2C%20support%20for%20.NET%205%20applications%20will%20be%20added%20in%20the%20Service%20Fabric%208.0%20release.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe've%20been%20waiting%20for%20the%20.NET5%20release%2C%20and%20so%20this%20feels%20like%20a%20sucker%20punch.%20Are%20you%20guys%20explicitly%20stating%20service%20fabric%20apps%20won't%20run%20or%20is%20this%20some%20sort%20of%20%22cover%20your%20**bleep**%22%20in%20case%20something%20pops%20up.%20Regardless%2C%20it's%20simply%20unacceptable%20to%20toss%20this%20out%20there%20at%20the%20last%20minute.%20Seriously%2C%20did%20.NET5%20release%20catch%20you%20guys%20off%20guard%3F%20%22Like%2C%20wow%2C%20we%20had%20no%20idea%20the%20.NET%20team%20intended%20to%20release%20new%20versions.%22%20Microsoft%20states%20that%20services%20have%20been%20running%20the%20.NET5%20previews%20for%20months.%20Microsoft%20also%20states%20that%20Service%20Fabric%20is%20the%20underpinning%20of%20Azure.%20Kind%20of%20seems%20like%20conflicting%20information.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EService%20Fabric%20is%20feeling%20more%20and%20more%20like%20an%20orphaned%20after%20thought.%20I%20created%20a%20service%20ticket%20a%20month%20ago%2C%20where%20the%20azure%20support%20guys%20were%20clearly%20ticked%20off%20at%20the%20SF%20team%20for%20their%20ineptness.%20I%20mentioned%20in%20the%20ticket%20that%20I%20had%20created%20this%20issue%20on%20github%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fservice-fabric%2Fissues%2F1038%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2Fmicrosoft%2Fservice-fabric%2Fissues%2F1038%3C%2FA%3E%26nbsp%3Bso%20they%20basically%20handed%20it%20off%20to%20the%20SF%20team%20for%20resolution.%20In%20the%20three%20weeks%20since%2C%20after%20an%20initial%20query%2C%20there%20has%20been%20ABSOLUTELY%20ZERO%20feedback%20from%20the%20SF%20team.%20Is%20that%20acceptable%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20said%20it%20before%2C%20and%20I'll%20say%20it%20again.%20The%20SF%20team%20needs%20a%20major%20kick%20in%20the%20**bleep**%20when%20it%20comes%20to%20community%20engagement.%20Someone%20is%20not%20doing%20their%20job.%20Seriously%2C%20just%20look%20what%20I%20said%20on%20this%20thread%2C%20and%20tell%20me%20I'm%20wrong.%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fservice-fabric%2Fissues%2F1058%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2Fmicrosoft%2Fservice-fabric%2Fissues%2F1058%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1874738%22%20slang%3D%22en-US%22%3EAzure%20Service%20Fabric%207.2%20Second%20Refresh%20Release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1874738%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20Azure%20Service%20Fabric%207.2%20second%20refresh%20release%20includes%20stability%20fixes%20for%20standalone%2C%20and%20Azure%20environments%20and%20has%20started%20rolling%20out%20to%20the%20various%20Azure%20regions.%20The%20updates%20for%20.NET%20SDK%2C%20Java%20SDK%20and%20Service%20Fabric%20Runtime%20will%20be%20available%20through%20Web%20Platform%20Installer%2C%20NuGet%20packages%20and%20Maven%20repositories%20in%207-10%20days%20within%20all%20regions.%20This%20update%20is%20now%20rolling%20out%20for%20Windows.%20SDK%20and%20Standalone%20packages%20will%20become%20available%20later%20this%20week.%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EService%20Fabric%20Runtime%3C%2FLI%3E%0A%3CUL%3E%0A%3CLI%3EWindows%20%E2%80%93%207.2.432.9590%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%20Ubuntu%2016%20-%26nbsp%3B%3CSPAN%20class%3D%22x%20x-first%20x-last%22%3E7.2.431.1%3C%2FSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EUbuntu%2018%20-%26nbsp%3B7.2.431.1804%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3EService%20Fabric%20for%20Windows%20Server%20Service%20Fabric%20Standalone%20Installer%20Package%20-%26nbsp%3B7.2.432.9590%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FUL%3E%0A%3CUL%3E%0A%3CLI%3E.NET%20SDK%3C%2FLI%3E%0A%3CUL%3E%0A%3CLI%3EWindows%20.NET%20SDK%20-%26nbsp%3B%26nbsp%3B%3CEM%3ENA%3C%2FEM%3E%3C%2FLI%3E%0A%3CLI%3EMicrosoft.ServiceFabric%20-%26nbsp%3B%3CEM%3E%26nbsp%3B%3C%2FEM%3E7.2.432%3CEM%3E%26nbsp%3B%3C%2FEM%3E%3C%2FLI%3E%0A%3CLI%3EReliable%20Services%20and%20Reliable%20Actors%20-%26nbsp%3B%3CEM%3E%26nbsp%3B%3C%2FEM%3E4.2.432%3C%2FLI%3E%0A%3CLI%3EASP.NET%20Core%20Service%20Fabric%20integration%20-%26nbsp%3B%3CEM%3E%26nbsp%3B%3C%2FEM%3E4.2.432%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CLI%3EJava%20SDK%20%E2%80%93%26nbsp%3B%201.0.6%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3EKey%20Announcements%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CDIV%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3EThis%26nbsp%3Brelease%26nbsp%3Bfixes%26nbsp%3Bstability%26nbsp%3Bissues%26nbsp%3Bintroduced%26nbsp%3Bto%26nbsp%3BFabricDNS%26nbsp%3Bin%26nbsp%3Bthe%26nbsp%3B7.2%26nbsp%3Brelease.%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%20style%3D%22font-family%3A%20inherit%3B%22%3EFor%20more%20details%2C%20please%20read%20the%20%3C%2FSPAN%3E%3CA%20style%3D%22font-family%3A%20inherit%3B%20background-color%3A%20%23ffffff%3B%22%20href%3D%22https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fservice-fabric%2Fblob%2Fmaster%2Frelease_notes%2FService-Fabric-72CU2-releasenotes.md%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Erelease%20notes%3C%2FA%3E%3CSPAN%20style%3D%22font-family%3A%20inherit%3B%22%3E.%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20face%3D%22inherit%22%3EWe%20are%20also%20making%20two%20releases%20available%20as%20manual%20%3C%2FFONT%3Eupgrade%3CFONT%20face%3D%22inherit%22%3E%26nbsp%3Bonly%20at%20this%20time.%26nbsp%3B%20See%20Additional%20Announcements%20below%20for%20more%20details.%26nbsp%3B%3C%2FFONT%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CFONT%20face%3D%22inherit%22%3EAdditional%20Announcements%26nbsp%3B%3C%2FFONT%3E%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSTRONG%3E7.2.433.9590%3C%2FSTRONG%3E%26nbsp%3B%20-%207.2%20CU3%20for%20Windows%20will%20be%20available%20through%20manual%20upgrades%20only.%20This%20release%20includes%20an%20additional%20fix%20for%20a%20memory%20leak%20in%20very%20specific%20scenarios%20when%20using%20remoting%20V2%20and%20creating%20and%20destroying%20services%20dynamically.%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3E7.1.503.9590%20-%20%3C%2FSTRONG%3E7.1%20CU8%20for%20Windows%20will%20be%20available%20through%20manual%20upgrades%20only.%20This%20release%20includes%20a%20fix%20for%20an%20assert%20that%20happens%20because%20an%20error%20code%20was%20not%20read%2Fchecked.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1874738%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20Azure%20Service%20Fabric%207.2%20second%20refresh%20release%20includes%20stability%20fixes%20for%20standalone%2C%20and%20Azure%20environments%20and%20has%20started%20rolling%20out%20to%20the%20various%20Azure%20regions.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1907113%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20Service%20Fabric%207.2%20Second%20Refresh%20Release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1907113%22%20slang%3D%22en-US%22%3E%3CP%3EAre%20there%20going%20to%20be%207.2%2F4.2%20nuget%20package%20releases%20and%20Web%20Platform%20Installers%20releases%20of%20the%20SDK.%26nbsp%3B%20It%20has%20been%20almost%20a%20month%20since%20the%20initial%207.2%2F4.2%20release%20and%20now%20over%20a%20week%20since%20the%20second%20refresh%2C%20and%20still%20nothing%20newer%20than%207.1%2F4.1%20for%20the%20nuget%20packages%20and%20SDK.%26nbsp%3B%20Also%2C%20when%20can%20we%20expect%20the%20second%20refresh%20to%20be%20pushed%20out%20to%20Stand-alone%20clusters%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1909192%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20Service%20Fabric%207.2%20Second%20Refresh%20Release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1909192%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F352039%22%20target%3D%22_blank%22%3E%40cdonovan63%3C%2FA%3E%26nbsp%3Bthe%20new%20releases%20of%20the%20SDK%20are%20now%20available%20in%20the%20Web%20Platform%20Installer.%20I%20have%20now%20updated%20the%20release%20notes%20to%20include%20the%20download%20link%20for%20standalone%20clusters%2C%20and%20if%20you%20are%20running%20on%20automatic%20upgrades%20you%20should%20expect%20to%20receive%20the%20update%20in%20the%20next%20few%20days.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1909560%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20Service%20Fabric%207.2%20Second%20Refresh%20Release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1909560%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F352039%22%20target%3D%22_blank%22%3E%40cdonovan63%3C%2FA%3E%26nbsp%3BApparently%20the%20Service%20Fabric%20team%20has%20decided%2C%20WITHOUT%20SOLICITING%20FEEDBACK%20OR%20INFORMING%20ANYONE%2C%20to%20delay%20publishing%20of%20NuGet%20packages%20until%20after%20a%20release%20is%20fully%20deployed.%20The%20reasoning%20was%20that%20some%20developers%20were%20publishing%20updates%20prior%20to%20rollout%20complete.%20At%20least%20that's%20what%20they%20implied%20on%20twitter.%20Why%20the%20initial%207.2%20NuGet%20packages%20haven't%20been%20published%20is%20a%20mystery.%20I%20was%20told%20that%20their%20download%20location%20is%20somewhere%20in%20the%20release%20notes%2C%20but%20I've%20read%20them%20a%20couple%20times%2C%20and%20still%20have%20no%20clue%20where%20they%20can%20be%20downloaded.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20sum%20this%20up%2C%20because%20some%20devs%20new%20to%20SF%20were%20accidently%20publishing%20prior%20to%20rollout%20complete%2C%20the%20SF%20team%20has%20decided%20to%20make%20it%20significantly%20more%20difficult%20%2F%20impossible%20for%20all%20SF%20developers%20to%20find%20%2F%20install%20%2F%20use%20updated%20NuGet%20packages.%20And%20they%20did%20this%20without%20telling%20anyone%2C%20and%20despite%20it%20obviously%20causing%20confusion%2C%20they're%20still%20treating%20it%20like%20a%20secret.%26nbsp%3BTo%20the%20SF%20team%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETHIS%20IS%20A%20BLOG%2C%20YOU'RE%20ALLOWED%20TO%20UPDATE%20IT%20MORE%20THAN%20ONCE%20A%20MONTH.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

The Azure Service Fabric 7.2 second refresh release includes stability fixes for standalone, and Azure environments and has started rolling out to the various Azure regions. The updates for .NET SDK, Java SDK and Service Fabric Runtime will be available through Web Platform Installer, NuGet packages and Maven repositories in 7-10 days within all regions. This update is now rolling out for Windows. SDK and Standalone packages will become available later this week.

  • Service Fabric Runtime
    • Windows – 7.2.432.9590
    • Ubuntu 16 - 7.2.431.1 
    • Ubuntu 18 - 7.2.431.1804
    • Service Fabric for Windows Server Service Fabric Standalone Installer Package - 7.2.432.9590
  • .NET SDK
    • Windows .NET SDK -  NA
    • Microsoft.ServiceFabric -  7.2.432 
    • Reliable Services and Reliable Actors -  4.2.432
    • ASP.NET Core Service Fabric integration -  4.2.432
  • Java SDK –  1.0.6

Key Announcements

  • This release fixes stability issues introduced to FabricDNS in the 7.2 release. For more details, please read the release notes.  
  • We are also making two releases available as manual upgrade only at this time.  See Additional Announcements below for more details. 

 

Additional Announcements 

  • 7.2.433.9590  - 7.2 CU3 for Windows will be available through manual upgrades only. This release includes an additional fix for a memory leak in very specific scenarios when using remoting V2 and creating and destroying services dynamically. 
  • 7.1.503.9590 - 7.1 CU8 for Windows will be available through manual upgrades only. This release includes a fix for an assert that happens because an error code was not read/checked.
9 Comments
Senior Member

Ok guys, you REALLY REALLY need to get your acts together.

 

So it's readily apparent that you messed up with 7.2.413.9590, not great, but not the end of the world. Someone NEEDS to update the Service Fabric release schedule here...

 

https://github.com/Microsoft/service-fabric

 

It still has September 2020 as the release date for 7.2. I just read the above release notes, and it states no support for .NET5 until v8. When can we expect v8 to be available?

Microsoft

@AdmiralBond we expect to release 8.0 in the spring of 2021. We are currently targeting March. I have gone ahead and updated the roadmap to better reflect our upcoming timelines. 

Senior Member

Can we get clarification on .NET5 compatibility? The release notes state,

 

".NET 5 apps are currently not supported, support for .NET 5 applications will be added in the Service Fabric 8.0 release."

 

We've been waiting for the .NET5 release, and so this feels like a sucker punch. Are you guys explicitly stating service fabric apps won't run or is this some sort of "cover your **bleep**" in case something pops up. Regardless, it's simply unacceptable to toss this out there at the last minute. Seriously, did .NET5 release catch you guys off guard? "Like, wow, we had no idea the .NET team intended to release new versions." Microsoft states that services have been running the .NET5 previews for months. Microsoft also states that Service Fabric is the underpinning of Azure. Kind of seems like conflicting information.

 

Service Fabric is feeling more and more like an orphaned after thought. I created a service ticket a month ago, where the azure support guys were clearly ticked off at the SF team for their ineptness. I mentioned in the ticket that I had created this issue on github, https://github.com/microsoft/service-fabric/issues/1038 so they basically handed it off to the SF team for resolution. In the three weeks since, after an initial query, there has been ABSOLUTELY ZERO feedback from the SF team. Is that acceptable?

 

I've said it before, and I'll say it again. The SF team needs a major kick in the **bleep** when it comes to community engagement. Someone is not doing their job. Seriously, just look what I said on this thread, and tell me I'm wrong. https://github.com/microsoft/service-fabric/issues/1058 

Senior Member

Are there going to be 7.2/4.2 nuget package releases and Web Platform Installers releases of the SDK.  It has been almost a month since the initial 7.2/4.2 release and now over a week since the second refresh, and still nothing newer than 7.1/4.1 for the nuget packages and SDK.  Also, when can we expect the second refresh to be pushed out to Stand-alone clusters?

Microsoft

@cdonovan63 the new releases of the SDK are now available in the Web Platform Installer. I have now updated the release notes to include the download link for standalone clusters, and if you are running on automatic upgrades you should expect to receive the update in the next few days. 

Senior Member

@cdonovan63 Apparently the Service Fabric team has decided, WITHOUT SOLICITING FEEDBACK OR INFORMING ANYONE, to delay publishing of NuGet packages until after a release is fully deployed. The reasoning was that some developers were publishing updates prior to rollout complete. At least that's what they implied on twitter. Why the initial 7.2 NuGet packages haven't been published is a mystery. I was told that their download location is somewhere in the release notes, but I've read them a couple times, and still have no clue where they can be downloaded.

 

To sum this up, because some devs new to SF were accidently publishing prior to rollout complete, the SF team has decided to make it significantly more difficult / impossible for all SF developers to find / install / use updated NuGet packages. And they did this without telling anyone, and despite it obviously causing confusion, they're still treating it like a secret. To the SF team, 

 

THIS IS A BLOG, YOU'RE ALLOWED TO UPDATE IT MORE THAN ONCE A MONTH.

Senior Member

Ok, it looks like the packages for 7.2.434 are out, https://www.nuget.org/packages/Microsoft.ServiceFabric/ 

 

Will you guys be uploading the 7.2.413 packages as well?

Senior Member

Are the 7.2.434 packages compatible with 7.2.433.9590? Or will there be a 7.2.434.9590 rollout?

 

PLEASE PLEASE PLEASE guys, it's literally impossible to develop against / maintain a Service Fabric cluster without better communication.

Microsoft

Yes the 7.2.434 packages are compatible with 7.2*, there will not be any 7.2.413 packages.