Skip to content

Latest commit

 

History

History
35 lines (24 loc) · 1.71 KB

some-net-apis-cause-first-chance-handled-entrypointnotfoundexceptions.md

File metadata and controls

35 lines (24 loc) · 1.71 KB

Some .NET APIs cause first chance (handled) EntryPointNotFoundExceptions

Details

In the .NET Framework 4.5, a small number of .NET methods began throwing first chance xref:System.EntryPointNotFoundException?displayProperty=fullNames. These exceptions were handled within the .NET Framework, but could break test automation that did not expect the first chance exceptions. These same APIs break some ApiVerifier scenarios when HighVersionLie is enabled.

Suggestion

This bug can be avoided by upgrading to .NET Framework 4.5.1. Alternatively, test automation can be updated to not break on first-chance xref:System.EntryPointNotFoundException?displayProperty=fullName exceptions.

Value
Scope Edge
Version 4.5
Type Runtime

Affected APIs

  • xref:System.Diagnostics.Debug.Assert(System.Boolean)?displayProperty=nameWithType
  • xref:System.Diagnostics.Debug.Assert(System.Boolean,System.String)?displayProperty=nameWithType
  • xref:System.Diagnostics.Debug.Assert(System.Boolean,System.String,System.String)?displayProperty=nameWithType
  • xref:System.Diagnostics.Debug.Assert(System.Boolean,System.String,System.String,System.Object[])?displayProperty=nameWithType
  • xref:System.Xml.Serialization.XmlSerializer.%23ctor(System.Type)