Skip to content

Commit 7f4869f

Browse files
Gnbrkm41gewarrenmairaw
committed
Update HandleProcessCorruptedStateExceptionsAttribute docs (#3335)
* Update HandleProcessCorruptedStateExceptions docs It appears that the handling of process corruption exceptions are not supported by design, and this attribute has no effect (https://github.com/dotnet/coreclr/issues/9045#issuecomment-290159433). To avoid confusion the documentation should be updated to reflect this .NET Core specific behaviour. Related: #3051 * Grammar fix * Update xml/System.Runtime.ExceptionServices/HandleProcessCorruptedStateExceptionsAttribute.xml Apply suggestions Co-Authored-By: Genevieve Warren <[email protected]> * small edit Co-authored-by: Genevieve Warren <[email protected]> Co-authored-by: Maira Wenzel <[email protected]>
1 parent 200d542 commit 7f4869f

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

xml/System.Runtime.ExceptionServices/HandleProcessCorruptedStateExceptionsAttribute.xml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,9 @@
4343
You can also add the [\<legacyCorruptedStateExceptionsPolicy>](~/docs/framework/configure-apps/file-schema/runtime/legacycorruptedstateexceptionspolicy-element.md) element to your application's configuration file. This will ensure that corrupted state exceptions are delivered to your exception handlers without the <xref:System.Runtime.ExceptionServices.HandleProcessCorruptedStateExceptionsAttribute> or <xref:System.Security.SecurityCriticalAttribute> attribute. This configuration element has no effect on applications that were compiled in versions previous to the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] but are running in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] or later; corrupted state exceptions will continue to be delivered for those applications. The <xref:System.Runtime.ExceptionServices.HandleProcessCorruptedStateExceptionsAttribute> attribute is ignored when it is encountered in partially trusted or transparent code, because a trusted host should not allow an untrusted add-in to catch and ignore these serious exceptions.
4444
4545
For more information about corrupted process state exceptions, see the entry [Handling Corrupted State Exceptions](https://go.microsoft.com/fwlink/?LinkID=179681) in the CLR Inside Out blog.
46-
46+
47+
**.NET Core only:** Even though this attribute exists in .NET Core, since the recovery from corrupted process state exceptions is not supported, this attribute is ignored. The CLR doesn't deliver corrupted process state exceptions to the managed code.
48+
4749
]]></format>
4850
</remarks>
4951
</Docs>

0 commit comments

Comments
 (0)