Skip to content

Conversation

@davidfowl
Copy link
Member

This came up when investigating why unity was broken on 2.2. The container instance passed to singleton isn't the scoped service provider.

Closes #1301

@pranavkm
Copy link

Do we need to follow up with Unity to have them fix this?

@davidfowl
Copy link
Member Author

Do we need to follow up with Unity to have them fix this?

Look at the linked bug.

@davidfowl davidfowl merged commit 732d143 into master Aug 28, 2019
@ghost ghost deleted the davidfowl/singletonfromscoped branch August 28, 2019 16:02
maryamariyan pushed a commit to maryamariyan/runtime that referenced this pull request Mar 17, 2020
dotnet/extensions#2236)

* Added verification test for resolving singleton from scoped container.

* Skip failing test with the Unity container


Commit migrated from dotnet/extensions@732d143
maryamariyan pushed a commit to maryamariyan/runtime that referenced this pull request Mar 27, 2020
dotnet/extensions#2236)

* Added verification test for resolving singleton from scoped container.

* Skip failing test with the Unity container


Commit migrated from dotnet/extensions@732d143
maryamariyan pushed a commit to maryamariyan/runtime that referenced this pull request Apr 13, 2020
dotnet/extensions#2236)

* Added verification test for resolving singleton from scoped container.

* Skip failing test with the Unity container


Commit migrated from dotnet/extensions@732d143
@ghost ghost locked as resolved and limited conversation to collaborators May 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Crash on page reload (Pressing F5) in ASP.Net.Core 2.2 while using Unity container

6 participants