New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow stack traces to be reported in .NET Standard 2.0 version of Simple Injector #369

Closed
dotnetjunkie opened this Issue Jan 11, 2017 · 0 comments

Comments

1 participant
@dotnetjunkie
Collaborator

dotnetjunkie commented Jan 11, 2017

The .NET 4.0 and .NET 4.5 versions of Simple Injector include a stack trace in the exception message that gets thrown when when the user tries to register to a locked container. The stack trace contains information about the call that locked the container. Likewise, issue #368 will ensure a stack trace is added that points to the call graph that caused the container to be disposed.

The .NETStandard compatible versions of Simple Injector do not have this behavior. Although it's impossible to add this behavior in .NET Standard 1.0, this feature can be made available in the .NET Standard 2.0 version of Simple Injector.

@dotnetjunkie dotnetjunkie added this to the v4 milestone Jan 11, 2017

@dotnetjunkie dotnetjunkie self-assigned this Jan 11, 2017

@dotnetjunkie dotnetjunkie modified the milestones: Backlog, v4 Jan 11, 2017

@dotnetjunkie dotnetjunkie changed the title from Allow stack traces to be reported in .NET Standard 1.3 version of Simple Injector to Allow stack traces to be reported in .NET Standard 2.0 version of Simple Injector Jan 11, 2017

@dotnetjunkie dotnetjunkie modified the milestones: Backlog, v4.1 Sep 17, 2017

@dotnetjunkie dotnetjunkie modified the milestones: v4.1, v4.2 Feb 28, 2018

@dotnetjunkie dotnetjunkie modified the milestones: v4.2, Backlog Apr 26, 2018

@dotnetjunkie dotnetjunkie modified the milestones: Backlog, v4.4 May 29, 2018

dotnetjunkie added a commit that referenced this issue Jul 17, 2018

Container locked and container disposed exceptions now include the or…
…iginating stack trace in .NETStandard 2.0. Fixes #369
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment