Open
Document .NET 11 Assembly.GetCallingAssembly behavior with StackTraceSupport=false#55213
Assembly.GetCallingAssembly behavior with StackTraceSupport=false#55213Conversation
3 tasks
Copilot
AI
changed the title
[WIP] Fix Assembly.GetCallingAssembly() behavior changes for stack-trace-disabled
Document .NET 11 Aug 3, 2026
Assembly.GetCallingAssembly behavior with StackTraceSupport=false
gewarren
reviewed
Aug 3, 2026
gewarren
left a comment
Collaborator
There was a problem hiding this comment.
Does https://github.com/dotnet/docs/blob/main/docs/core/compatibility/unsupported-apis.md?plain=1 need to be updated too?
gewarren
marked this pull request as ready for review
August 3, 2026 22:10
Collaborator
|
@copilot Please respond to feedback. |
Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
gewarren
approved these changes
Aug 3, 2026
gewarren
reviewed
Aug 3, 2026
|
|
||
| ## New behavior | ||
|
|
||
| Starting in .NET 11, on Native AOT, <xref:System.Reflection.Assembly.GetCallingAssembly?displayProperty=nameWithType> returns the calling assembly by inspecting stack trace data. Starting in .NET 11, on both Native AOT and CoreCLR, the method throws <xref:System.NotSupportedException> if `StackTrace.IsSupported` is `false`, for example when the `StackTraceSupport` feature switch is set to `false`. |
Collaborator
There was a problem hiding this comment.
Waiting to see if StackTrace.IsSupported can be an xref or what exactly it refers to.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
.NET 11 Preview 7changesAssembly.GetCallingAssembly()semantics: Native AOT now supports caller resolution, and both Native AOT and CoreCLR now throwNotSupportedExceptionwhen stack trace support is disabled. This PR adds the corresponding breaking-change documentation and links it into the .NET 11 compatibility surface.Breaking change article (new)
docs/core/compatibility/core-libraries/11/assembly-getcallingassembly-stacktracesupport-disabled.md.System.Reflection.Assembly.GetCallingAssembly)..NET 11 compatibility index update
docs/core/compatibility/11.mdso the change appears in the version rollup.TOC integration
docs/core/compatibility/toc.ymlunder .NET 11 > Core .NET libraries.Related feature-switch guidance
docs/core/deploying/trimming/trimming-options.mdto note thatStackTraceSupport=falsecausesAssembly.GetCallingAssembly()to throwNotSupportedExceptionin .NET 11+.Internal previews