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

Open
dotnetjunkie opened this Issue Jan 11, 2017 · 1 comment

Projects

None yet

1 participant

@dotnetjunkie
Collaborator

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 1.3 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 milestone: Backlog, v4 Jan 11, 2017
@dotnetjunkie
Collaborator

Unfortunately, it seems that the StackTrace class will only be available in .NET Standard 2.0; not in .NET Standard 1.3.

@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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment