Bug 41279 - Wrong syntax used for nested types in MethodAccessException (and similar)
Summary: Wrong syntax used for nested types in MethodAccessException (and similar)
Alias: None
Product: Runtime
Classification: Mono
Component: JIT (show other bugs)
Version: unspecified
Hardware: PC Mac OS
: Low minor
Target Milestone: Future Cycle (TBD)
Assignee: Rodrigo Kumpera
Depends on:
Reported: 2016-05-24 09:42 UTC by Marek Safar
Modified: 2017-08-18 20:09 UTC (History)
3 users (show)

See Also:
Is this bug a regression?: ---
Last known good build:


Description Marek Safar 2016-05-24 09:42:30 UTC
For example

System.MethodAccessException: Method `Ex:Private ()' is inaccessible from method `X/<Foo>c__async0:MoveNext ()'

uses wrong '/' separator for nested types. It should be '+'. Similarly ':' is used instead of '.' separator

.NET shows

System.MethodAccessException: Attempt by method 'X+<Foo>c__async0.MoveNext()' to access method 'Ex.Private()' failed.
Comment 1 Rodrigo Kumpera 2017-08-17 22:54:24 UTC
Comment 2 Rodrigo Kumpera 2017-08-18 20:09:05 UTC
Fixed in master

Notice (2018-05-21): bugzilla.xamarin.com will be switching to read-only mode on Thursday, 2018-05-25 22:00 UTC.

Please join us on Visual Studio Developer Community and GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs and copy them to the new locations as needed for follow-up. The See Also field on each Bugzilla bug will be updated with a link to its new location when applicable.

After Bugzilla is read-only, if you have new information to add for a bug that does not yet have a matching issue on Developer Community or GitHub, you can create a follow-up issue in the new location. Copy and paste the title and description from this bug, and then add your new details. You can get a pre-formatted version of the title and description here:

In special cases you might also want the comments:

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Note You need to log in before you can comment on or make changes to this bug.