You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 10, 2026. It is now read-only.
We have been struggling to find why our logging infrastructure based on ETW and System.Diagnostics.Tracing.EventSource didn't work on .NET Framework 4.6.1 but worked on .NET Framework 4.6.2.
We have found today that, apparently, the problem was caused by our EventSource class (not the public name set in EventSourceAttribute) being just named "our namespace".EventSource.
Now we are trying to find that constraint in the documentation, with no success.
Can anyone confirm there was such an undocumented restriction in .NET Framework 4.6.1 (removed in .NET Framework 4.6.2) for EventSource subclass names?
We have been struggling to find why our logging infrastructure based on ETW and System.Diagnostics.Tracing.EventSource didn't work on .NET Framework 4.6.1 but worked on .NET Framework 4.6.2.
We have found today that, apparently, the problem was caused by our EventSource class (not the public name set in EventSourceAttribute) being just named "our namespace".EventSource.
Now we are trying to find that constraint in the documentation, with no success.
Can anyone confirm there was such an undocumented restriction in .NET Framework 4.6.1 (removed in .NET Framework 4.6.2) for EventSource subclass names?
Thank you very much.