Skip to content

Latest commit

 

History

History
58 lines (42 loc) · 1.8 KB

workflow-xoml-file-checksums-changed-from-md5-to-sha256.md

File metadata and controls

58 lines (42 loc) · 1.8 KB
Raw

Workflow XOML file checksums changed from MD5 to SHA256

Scope

Minor

Version Introduced

4.8

Source Analyzer Status

NotPlanned

Change Description

To support debugging XOML-based workflows with Visual Studio, when workflow projects containing XOML files build, a checksum of the contents of the XOML file is included in the code generated as a xref:System.Workflow.ComponentModel.Compiler.WorkflowMarkupSourceAttribute.MD5Digest?displayProperty=nameWithType value. In the .NET Framework 4.7.2 and earlier versions, this checksum hashing used the MD5 algorithm, which caused issues on FIPS-enabled systems. Starting with the .NET Framework 4.8, the algorithm used is SHA256. To be compatible with the WorkflowMarkupSourceAttribute.MD5Digest, only the first 16 bytes of the generated checksum are used.

This may cause problems during debugging. You may need to re-build your project.

  • Quirked
  • Build-time break // Causes a break if attempted to recompile

Recommended Action

If re-building your project does not solve the problem, try setting the AppContext switch "Switch.System.Workflow.ComponentModel.UseLegacyHashForXomlFileChecksum" to true.

In code:

System.AppContext.SetSwitch("Switch.System.Workflow.ComponentModel.UseLegacyHashForXomlFileChecksum", true);

Or in a configuration file (this needs to be in MSBuild.exe.config for the MSBuild.exe that you are using):

<configuration>
   <runtime>
      <AppContextSwitchOverrides value="Switch.System.Workflow.ComponentModel.UseLegacyHashForXomlFileChecksum=true" /> 
   </runtime>
</configuration>

Affected APIs

  • Not detectable via API analysis

Category

Windows Workflow Foundation (WF)