dotnet/Documentation/compatibility/workflow-xaml-checksums-for-symbols-changed-from-sha1-to-sha256.md at edaab6cd2fd92f98c30044d7e6412c49feddf251

mirror of https://github.com/microsoft/dotnet.git synced 2025-12-25 01:02:53 -05:00

Files

Jim Carley 769df738ab Compat documents for .NET 4.8 for Workflow runtime and designer. (#966 )

* Compat documents for .NET 4.8 for Workflow runtime and designer.

* Addressed review comments

2019-02-27 10:22:25 -08:00

1.4 KiB

Raw Blame History

Workflow XAML checksums for symbols changed from SHA1 to SHA256

Scope

Minor

Version Introduced

4.8

Source Analyzer Status

NotPlanned

Change Description

To support debugging with Visual Studio, the Workflow runtime generates a checksum for a workflow XAML file using a hashing algorithm. In the .NET Framework 4.6.2 and earlier versions, workflow checksum hashing used the MD5 algorithm, which caused issues on FIPS-enabled systems. Starting with the .NET Framework 4.7, the default algorithm was changed to SHA1. Starting with the .NET Framework 4.8, the default algorithm was changed to SHA256.

Quirked
Build-time break

Recommended Action

If your code is unable to load workflow instances or to find appropriate symbols due to a checksum failure, try setting the AppContext switch "Switch.System.Activities.UseSHA1HashForDebuggerSymbols" to true.

In code:

System.AppContext.SetSwitch("Switch.System.Activities.UseSHA1HashForDebuggerSymbols", true);

Or in configuration:

<configuration>
   <runtime>
      <AppContextSwitchOverrides value="Switch.System.Activities.UseSHA1HashForDebuggerSymbols=true" /> 
   </runtime>
</configuration>

Affected APIs

Not detectable via API analysis

1.4 KiB Raw Blame History