Lang Cheng

@singha-rayathong Have you found the solution? I also encountered this issue.

@fMichaleczek Thanks for reply. Microsoft.PowerShell.SDK 7.4.0 => System.Management.Automation 7.4.0 => Newtonsoft.Json 13.0.3 SDK automatically references the latest Newtonsoft.Json as part of its dependency, I can confirm its >= 13.0.3.

The default behavior of MSBuild is load the lowest possible version for indirect dependency. Also, the latest version of Newtonsoft.Json is indeed 13.0.3, thus the loaded one is 13.0.3

@jeffhandley Thanks for the quick update! How about deserialization? What would be the proper way to do so?

+1 here. We are trying to reference this project in our MSFT internal application, but it also requires strong name.

@ardalis Hi, thanks for the quick feedback. I was running the internal package publishing tool and hit the following error message: WARNING: File not StrongName signed: lib\netstandard2.0\Ardalis.Specification.dll ERROR: File not...

Hi @ardalis It seems like publishing package with target framework version above netcore, strong name is not required. Could you please add multi-target to Ardalis.Specification with netstandard2.0 and net6.0? https://docs.microsoft.com/en-us/dotnet/standard/assembly/strong-named...

   @ardalis I think you have looked into a very old thread. According to our internal tool, both MediatR and MediatR.Contracts are strong name signed. But would you...