RetainPhil

Work around we figured out that seems to do the trick for me. Modify Publish-NewServiceFabricApplication.ps1 in the ServiceFabricSDK to set up a symlink between artifacts and target instead of **Copy-ServiceFabricApplicationPackage**...

Why's VS still directing us to use WPI to install SF sdk anyway? The software is about to be shelved in a couple of months right? https://blogs.iis.net/iisteam/web-platform-installer-end-of-support-feed

Unfortunately for me - I'm now reproducing this issue on a second machine. The issue started occuring after re-installing Web Platform Installer on the second machine. Here's logs from WPI:...

I tried both VS2019 & VS2022 - made no difference. In the end I manually downloaded the runtime installer (e.g. MicrosoftServiceFabric.8.2.1571.9590.exe) fromdirect download link in the release notes and run...

Slightly more info on this - I narrowed down the problem to extraction of self-extracting archive MicrosoftServiceFabricAutoextractor.exe - it seems like this extractor is based on unsupported program "extract.exe" in...

I'm running into a problem with this issue too. For me it seems to be related to[ this commit](https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/commit/922901505740480f3fe6349e501ad36082e441e3), which was released in version 6.15.1 of both [System.IdentityModel.Tokens.Jwt](https://www.nuget.org/packages/System.IdentityModel.Tokens.Jwt/) and [Microsoft.IdentityModel.Tokens](https://www.nuget.org/packages/Microsoft.IdentityModel.Tokens/)...

Our Azure Build VM images were all upgraded from **Current image version: '20221027.1'** to **Current image version: '20221120.1'** yesterday which now has VS 17.4 and .net7 sdk installed and hence,...

Same thing for us - since it looks like our VM images were all upgraded from Current image version: '20221027.1' to Current image version: '20221120.1' yesterday which now has VS...