Add [DebuggerGuidedStepThrough] to new invoker methods

[steveharter]

Add these missing attributes to make the newly added invoker APIs consistent with the standard invoke APIs in NativeAOT.

CoreClr info: using "Just My Code" does work with the newly added invoker APIs for CoreClr; that is, you can step into the invoked method. With "Just My Code" off, however, the stepped-into method is hit-or-miss for both the new invoker APIs as well as the existing ones (one of the internal framework methods will be stepped into). We could add [DebuggerHidden] and [DebuggerStepThrough] to more methods to make step-in work when "Just My Code" is off, like we already have in the standard invoke code, although in general that doesn't work either and\or is fragile due to reflection calling non-reflection code such as in Span, Signature, etc. which would also need these attributes.

[ghost]

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Add these missing attributes to make the newly added invoker APIs consistent with the standard invoke APIs in NativeAOT.

CoreClr info: using "Just My Code" does work with the newly added invoker APIs for CoreClr; that is, you can step into the invoked method. With "Just My Code" off, however, the stepped-into method is hit-or-miss for both the new invoker APIs as well as the existing ones (one of the internal framework methods will be stepped into). We could add [DebuggerHidden] and [DebuggerStepThrough] to make step-in work when "Just My Code" is off, although in general that is fragile due to calling many non-reflection scenarios.

Author:	steveharter
Assignees:	steveharter
Labels:	area-System.Reflection, area-NativeAOT-coreclr
Milestone:	-

[jkotas]

Does this change cause any observable behavior under unmanaged debugger that's the only debugging story for native AOT at the moment?

[MichalStrehovsky]

Does this change cause any observable behavior under unmanaged debugger that's the only debugging story for native AOT at the moment?

Native AOT currently doesn't respect this (the attribute is a leftover from .NET Native). It should be possible to make this work on Windows with 0xF00F00/0xFEEFEE magic line numbers, but I'm not aware of a way to make this work outside Windows so the priority of implementing this is lower right now since we can't make it work crossplat.

[steveharter]

@MichalStrehovsky feel free to close this PR if it doesn't matter - I just created this PR for consistency.

[MichalStrehovsky]

@MichalStrehovsky feel free to close this PR if it doesn't matter - I just created this PR for consistency.

I don't mind either way - it's possible we'll want to fix this at some point. But to merge this, uses in ConstructorInvoker.cs will need to be updated to call PreviousCallContainsDebuggerStepInCode, similar to how it's called in MethodInvoker.cs.

[MichalStrehovsky]

Thank you!

[steveharter]

Add these missing attributes to make the newly added invoker APIs consistent with the standard invoke APIs in NativeAOT.

CoreClr info: using "Just My Code" does work with the newly added invoker APIs for CoreClr; that is, you can step into the invoked method. With "Just My Code" off, however, the stepped-into method is hit-or-miss for both the new invoker APIs as well as the existing ones (one of the internal framework methods will be stepped into). We could add [DebuggerHidden] and [DebuggerStepThrough] to more methods to make step-in work when "Just My Code" is off, like we already have in the standard invoke code, although in general that doesn't work either and\or is fragile due to reflection calling non-reflection code such as in Span, Signature, etc. which would also need these attributes.

[ghost]

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Add these missing attributes to make the newly added invoker APIs consistent with the standard invoke APIs in NativeAOT.

CoreClr info: using "Just My Code" does work with the newly added invoker APIs for CoreClr; that is, you can step into the invoked method. With "Just My Code" off, however, the stepped-into method is hit-or-miss for both the new invoker APIs as well as the existing ones (one of the internal framework methods will be stepped into). We could add [DebuggerHidden] and [DebuggerStepThrough] to make step-in work when "Just My Code" is off, although in general that is fragile due to calling many non-reflection scenarios.

Author:	steveharter
Assignees:	steveharter
Labels:	area-System.Reflection, area-NativeAOT-coreclr
Milestone:	-

[jkotas]

Does this change cause any observable behavior under unmanaged debugger that's the only debugging story for native AOT at the moment?

[MichalStrehovsky]

Does this change cause any observable behavior under unmanaged debugger that's the only debugging story for native AOT at the moment?

Native AOT currently doesn't respect this (the attribute is a leftover from .NET Native). It should be possible to make this work on Windows with 0xF00F00/0xFEEFEE magic line numbers, but I'm not aware of a way to make this work outside Windows so the priority of implementing this is lower right now since we can't make it work crossplat.

[steveharter]

@MichalStrehovsky feel free to close this PR if it doesn't matter - I just created this PR for consistency.

[MichalStrehovsky]

@MichalStrehovsky feel free to close this PR if it doesn't matter - I just created this PR for consistency.

I don't mind either way - it's possible we'll want to fix this at some point. But to merge this, uses in ConstructorInvoker.cs will need to be updated to call PreviousCallContainsDebuggerStepInCode, similar to how it's called in MethodInvoker.cs.

[MichalStrehovsky]

Thank you!

[steveharter]

Add these missing attributes to make the newly added invoker APIs consistent with the standard invoke APIs in NativeAOT.

CoreClr info: using "Just My Code" does work with the newly added invoker APIs for CoreClr; that is, you can step into the invoked method. With "Just My Code" off, however, the stepped-into method is hit-or-miss for both the new invoker APIs as well as the existing ones (one of the internal framework methods will be stepped into). We could add [DebuggerHidden] and [DebuggerStepThrough] to more methods to make step-in work when "Just My Code" is off, like we already have in the standard invoke code, although in general that doesn't work either and\or is fragile due to reflection calling non-reflection code such as in Span, Signature, etc. which would also need these attributes.

[ghost]

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Add these missing attributes to make the newly added invoker APIs consistent with the standard invoke APIs in NativeAOT.

CoreClr info: using "Just My Code" does work with the newly added invoker APIs for CoreClr; that is, you can step into the invoked method. With "Just My Code" off, however, the stepped-into method is hit-or-miss for both the new invoker APIs as well as the existing ones (one of the internal framework methods will be stepped into). We could add [DebuggerHidden] and [DebuggerStepThrough] to make step-in work when "Just My Code" is off, although in general that is fragile due to calling many non-reflection scenarios.

Author:	steveharter
Assignees:	steveharter
Labels:	area-System.Reflection, area-NativeAOT-coreclr
Milestone:	-

[jkotas]

Does this change cause any observable behavior under unmanaged debugger that's the only debugging story for native AOT at the moment?

[MichalStrehovsky]

Does this change cause any observable behavior under unmanaged debugger that's the only debugging story for native AOT at the moment?

Native AOT currently doesn't respect this (the attribute is a leftover from .NET Native). It should be possible to make this work on Windows with 0xF00F00/0xFEEFEE magic line numbers, but I'm not aware of a way to make this work outside Windows so the priority of implementing this is lower right now since we can't make it work crossplat.

[steveharter]

@MichalStrehovsky feel free to close this PR if it doesn't matter - I just created this PR for consistency.

[MichalStrehovsky]

@MichalStrehovsky feel free to close this PR if it doesn't matter - I just created this PR for consistency.

I don't mind either way - it's possible we'll want to fix this at some point. But to merge this, uses in ConstructorInvoker.cs will need to be updated to call PreviousCallContainsDebuggerStepInCode, similar to how it's called in MethodInvoker.cs.

[MichalStrehovsky]

Thank you!

[steveharter]

Add these missing attributes to make the newly added invoker APIs consistent with the standard invoke APIs in NativeAOT.

CoreClr info: using "Just My Code" does work with the newly added invoker APIs for CoreClr; that is, you can step into the invoked method. With "Just My Code" off, however, the stepped-into method is hit-or-miss for both the new invoker APIs as well as the existing ones (one of the internal framework methods will be stepped into). We could add [DebuggerHidden] and [DebuggerStepThrough] to more methods to make step-in work when "Just My Code" is off, like we already have in the standard invoke code, although in general that doesn't work either and\or is fragile due to reflection calling non-reflection code such as in Span, Signature, etc. which would also need these attributes.

[ghost]

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Add these missing attributes to make the newly added invoker APIs consistent with the standard invoke APIs in NativeAOT.

CoreClr info: using "Just My Code" does work with the newly added invoker APIs for CoreClr; that is, you can step into the invoked method. With "Just My Code" off, however, the stepped-into method is hit-or-miss for both the new invoker APIs as well as the existing ones (one of the internal framework methods will be stepped into). We could add [DebuggerHidden] and [DebuggerStepThrough] to make step-in work when "Just My Code" is off, although in general that is fragile due to calling many non-reflection scenarios.

Author:	steveharter
Assignees:	steveharter
Labels:	area-System.Reflection, area-NativeAOT-coreclr
Milestone:	-

[jkotas]

Does this change cause any observable behavior under unmanaged debugger that's the only debugging story for native AOT at the moment?

[MichalStrehovsky]

Does this change cause any observable behavior under unmanaged debugger that's the only debugging story for native AOT at the moment?

Native AOT currently doesn't respect this (the attribute is a leftover from .NET Native). It should be possible to make this work on Windows with 0xF00F00/0xFEEFEE magic line numbers, but I'm not aware of a way to make this work outside Windows so the priority of implementing this is lower right now since we can't make it work crossplat.

[steveharter]

@MichalStrehovsky feel free to close this PR if it doesn't matter - I just created this PR for consistency.

[MichalStrehovsky]

@MichalStrehovsky feel free to close this PR if it doesn't matter - I just created this PR for consistency.

I don't mind either way - it's possible we'll want to fix this at some point. But to merge this, uses in ConstructorInvoker.cs will need to be updated to call PreviousCallContainsDebuggerStepInCode, similar to how it's called in MethodInvoker.cs.

[MichalStrehovsky]

Thank you!

[steveharter]

Add these missing attributes to make the newly added invoker APIs consistent with the standard invoke APIs in NativeAOT.

CoreClr info: using "Just My Code" does work with the newly added invoker APIs for CoreClr; that is, you can step into the invoked method. With "Just My Code" off, however, the stepped-into method is hit-or-miss for both the new invoker APIs as well as the existing ones (one of the internal framework methods will be stepped into). We could add [DebuggerHidden] and [DebuggerStepThrough] to more methods to make step-in work when "Just My Code" is off, like we already have in the standard invoke code, although in general that doesn't work either and\or is fragile due to reflection calling non-reflection code such as in Span, Signature, etc. which would also need these attributes.

[ghost]

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Add these missing attributes to make the newly added invoker APIs consistent with the standard invoke APIs in NativeAOT.

CoreClr info: using "Just My Code" does work with the newly added invoker APIs for CoreClr; that is, you can step into the invoked method. With "Just My Code" off, however, the stepped-into method is hit-or-miss for both the new invoker APIs as well as the existing ones (one of the internal framework methods will be stepped into). We could add [DebuggerHidden] and [DebuggerStepThrough] to make step-in work when "Just My Code" is off, although in general that is fragile due to calling many non-reflection scenarios.

Author:	steveharter
Assignees:	steveharter
Labels:	area-System.Reflection, area-NativeAOT-coreclr
Milestone:	-

[jkotas]

Does this change cause any observable behavior under unmanaged debugger that's the only debugging story for native AOT at the moment?

[MichalStrehovsky]

Does this change cause any observable behavior under unmanaged debugger that's the only debugging story for native AOT at the moment?

Native AOT currently doesn't respect this (the attribute is a leftover from .NET Native). It should be possible to make this work on Windows with 0xF00F00/0xFEEFEE magic line numbers, but I'm not aware of a way to make this work outside Windows so the priority of implementing this is lower right now since we can't make it work crossplat.

[steveharter]

@MichalStrehovsky feel free to close this PR if it doesn't matter - I just created this PR for consistency.

[MichalStrehovsky]

@MichalStrehovsky feel free to close this PR if it doesn't matter - I just created this PR for consistency.

I don't mind either way - it's possible we'll want to fix this at some point. But to merge this, uses in ConstructorInvoker.cs will need to be updated to call PreviousCallContainsDebuggerStepInCode, similar to how it's called in MethodInvoker.cs.

[MichalStrehovsky]

Thank you!

[steveharter]

Add these missing attributes to make the newly added invoker APIs consistent with the standard invoke APIs in NativeAOT.

CoreClr info: using "Just My Code" does work with the newly added invoker APIs for CoreClr; that is, you can step into the invoked method. With "Just My Code" off, however, the stepped-into method is hit-or-miss for both the new invoker APIs as well as the existing ones (one of the internal framework methods will be stepped into). We could add [DebuggerHidden] and [DebuggerStepThrough] to more methods to make step-in work when "Just My Code" is off, like we already have in the standard invoke code, although in general that doesn't work either and\or is fragile due to reflection calling non-reflection code such as in Span, Signature, etc. which would also need these attributes.

[ghost]

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Add these missing attributes to make the newly added invoker APIs consistent with the standard invoke APIs in NativeAOT.

CoreClr info: using "Just My Code" does work with the newly added invoker APIs for CoreClr; that is, you can step into the invoked method. With "Just My Code" off, however, the stepped-into method is hit-or-miss for both the new invoker APIs as well as the existing ones (one of the internal framework methods will be stepped into). We could add [DebuggerHidden] and [DebuggerStepThrough] to make step-in work when "Just My Code" is off, although in general that is fragile due to calling many non-reflection scenarios.

Author:	steveharter
Assignees:	steveharter
Labels:	area-System.Reflection, area-NativeAOT-coreclr
Milestone:	-

[jkotas]

Does this change cause any observable behavior under unmanaged debugger that's the only debugging story for native AOT at the moment?

[MichalStrehovsky]

Does this change cause any observable behavior under unmanaged debugger that's the only debugging story for native AOT at the moment?

Native AOT currently doesn't respect this (the attribute is a leftover from .NET Native). It should be possible to make this work on Windows with 0xF00F00/0xFEEFEE magic line numbers, but I'm not aware of a way to make this work outside Windows so the priority of implementing this is lower right now since we can't make it work crossplat.

[steveharter]

@MichalStrehovsky feel free to close this PR if it doesn't matter - I just created this PR for consistency.

[MichalStrehovsky]

@MichalStrehovsky feel free to close this PR if it doesn't matter - I just created this PR for consistency.

I don't mind either way - it's possible we'll want to fix this at some point. But to merge this, uses in ConstructorInvoker.cs will need to be updated to call PreviousCallContainsDebuggerStepInCode, similar to how it's called in MethodInvoker.cs.

[MichalStrehovsky]

Thank you!

[steveharter]

Add these missing attributes to make the newly added invoker APIs consistent with the standard invoke APIs in NativeAOT.

CoreClr info: using "Just My Code" does work with the newly added invoker APIs for CoreClr; that is, you can step into the invoked method. With "Just My Code" off, however, the stepped-into method is hit-or-miss for both the new invoker APIs as well as the existing ones (one of the internal framework methods will be stepped into). We could add [DebuggerHidden] and [DebuggerStepThrough] to more methods to make step-in work when "Just My Code" is off, like we already have in the standard invoke code, although in general that doesn't work either and\or is fragile due to reflection calling non-reflection code such as in Span, Signature, etc. which would also need these attributes.

[ghost]

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Add these missing attributes to make the newly added invoker APIs consistent with the standard invoke APIs in NativeAOT.

CoreClr info: using "Just My Code" does work with the newly added invoker APIs for CoreClr; that is, you can step into the invoked method. With "Just My Code" off, however, the stepped-into method is hit-or-miss for both the new invoker APIs as well as the existing ones (one of the internal framework methods will be stepped into). We could add [DebuggerHidden] and [DebuggerStepThrough] to make step-in work when "Just My Code" is off, although in general that is fragile due to calling many non-reflection scenarios.

Author:	steveharter
Assignees:	steveharter
Labels:	area-System.Reflection, area-NativeAOT-coreclr
Milestone:	-

[jkotas]

Does this change cause any observable behavior under unmanaged debugger that's the only debugging story for native AOT at the moment?

[MichalStrehovsky]

Does this change cause any observable behavior under unmanaged debugger that's the only debugging story for native AOT at the moment?

Native AOT currently doesn't respect this (the attribute is a leftover from .NET Native). It should be possible to make this work on Windows with 0xF00F00/0xFEEFEE magic line numbers, but I'm not aware of a way to make this work outside Windows so the priority of implementing this is lower right now since we can't make it work crossplat.

[steveharter]

@MichalStrehovsky feel free to close this PR if it doesn't matter - I just created this PR for consistency.

[MichalStrehovsky]

@MichalStrehovsky feel free to close this PR if it doesn't matter - I just created this PR for consistency.

I don't mind either way - it's possible we'll want to fix this at some point. But to merge this, uses in ConstructorInvoker.cs will need to be updated to call PreviousCallContainsDebuggerStepInCode, similar to how it's called in MethodInvoker.cs.

[MichalStrehovsky]

Thank you!

[steveharter]

Add these missing attributes to make the newly added invoker APIs consistent with the standard invoke APIs in NativeAOT.

CoreClr info: using "Just My Code" does work with the newly added invoker APIs for CoreClr; that is, you can step into the invoked method. With "Just My Code" off, however, the stepped-into method is hit-or-miss for both the new invoker APIs as well as the existing ones (one of the internal framework methods will be stepped into). We could add [DebuggerHidden] and [DebuggerStepThrough] to more methods to make step-in work when "Just My Code" is off, like we already have in the standard invoke code, although in general that doesn't work either and\or is fragile due to reflection calling non-reflection code such as in Span, Signature, etc. which would also need these attributes.

[ghost]

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Add these missing attributes to make the newly added invoker APIs consistent with the standard invoke APIs in NativeAOT.

CoreClr info: using "Just My Code" does work with the newly added invoker APIs for CoreClr; that is, you can step into the invoked method. With "Just My Code" off, however, the stepped-into method is hit-or-miss for both the new invoker APIs as well as the existing ones (one of the internal framework methods will be stepped into). We could add [DebuggerHidden] and [DebuggerStepThrough] to make step-in work when "Just My Code" is off, although in general that is fragile due to calling many non-reflection scenarios.

Author:	steveharter
Assignees:	steveharter
Labels:	area-System.Reflection, area-NativeAOT-coreclr
Milestone:	-

[jkotas]

Does this change cause any observable behavior under unmanaged debugger that's the only debugging story for native AOT at the moment?

[MichalStrehovsky]

Does this change cause any observable behavior under unmanaged debugger that's the only debugging story for native AOT at the moment?

Native AOT currently doesn't respect this (the attribute is a leftover from .NET Native). It should be possible to make this work on Windows with 0xF00F00/0xFEEFEE magic line numbers, but I'm not aware of a way to make this work outside Windows so the priority of implementing this is lower right now since we can't make it work crossplat.

[steveharter]

@MichalStrehovsky feel free to close this PR if it doesn't matter - I just created this PR for consistency.

[MichalStrehovsky]

@MichalStrehovsky feel free to close this PR if it doesn't matter - I just created this PR for consistency.

I don't mind either way - it's possible we'll want to fix this at some point. But to merge this, uses in ConstructorInvoker.cs will need to be updated to call PreviousCallContainsDebuggerStepInCode, similar to how it's called in MethodInvoker.cs.

[MichalStrehovsky]

Thank you!