-
Notifications
You must be signed in to change notification settings - Fork 456
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
Update Castle.Windsor.Extensions.DependencyInjection to support .NET8 #668
base: master
Are you sure you want to change the base?
Commits on Feb 9, 2024
-
Refs: castleproject#646 Castle.Windsor.Extension.DepencencyInjection …
…removed null check on scope cache (AsyncLocal can be null on Threads coming from Threadpool.UnsafeQueueUserWorkItem, having no null check was also the original behavior)
Configuration menu - View commit details
-
Copy full SHA for 08ad3dc - Browse repository at this point
Copy the full SHA 08ad3dcView commit details -
ExtensionContainerRootsScopeAccessor might return a null root scope in
Threadpool.UnsafeQueueUserWorkItem.
Configuration menu - View commit details
-
Copy full SHA for a8347ea - Browse repository at this point
Copy the full SHA a8347eaView commit details -
Configuration menu - View commit details
-
Copy full SHA for ba03d1b - Browse repository at this point
Copy the full SHA ba03d1bView commit details -
Configuration menu - View commit details
-
Copy full SHA for df9dd36 - Browse repository at this point
Copy the full SHA df9dd36View commit details -
Configuration menu - View commit details
-
Copy full SHA for 64df1b0 - Browse repository at this point
Copy the full SHA 64df1b0View commit details -
Option to map custom NetStatic to Castle Singleton lifestyle.
this improve resolution of singleton object that might not need a root scope, the windsor container should be enough to resolve singletons
Configuration menu - View commit details
-
Copy full SHA for 28ac185 - Browse repository at this point
Copy the full SHA 28ac185View commit details -
RootScope AsyncLocal cache can be null when AspNetCore tries to create
scopes from Threadpool.UnsafeQueueUserWorkItem
Configuration menu - View commit details
-
Copy full SHA for a210c2a - Browse repository at this point
Copy the full SHA a210c2aView commit details -
Configuration menu - View commit details
-
Copy full SHA for b390405 - Browse repository at this point
Copy the full SHA b390405View commit details -
Configuration menu - View commit details
-
Copy full SHA for b997da0 - Browse repository at this point
Copy the full SHA b997da0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 5532539 - Browse repository at this point
Copy the full SHA 5532539View commit details -
Configuration menu - View commit details
-
Copy full SHA for 518cc84 - Browse repository at this point
Copy the full SHA 518cc84View commit details -
Configuration menu - View commit details
-
Copy full SHA for 81c6b05 - Browse repository at this point
Copy the full SHA 81c6b05View commit details
Commits on Feb 14, 2024
-
Update to work with .NET 8 dependency registration.
Major fix was to support keyed registration scenario
Configuration menu - View commit details
-
Copy full SHA for 3707b52 - Browse repository at this point
Copy the full SHA 3707b52View commit details
Commits on Feb 15, 2024
-
Fixed bug in missing root scope with orleans/kestrel.
The previous handling of root scope is wrong, the code set root scope in an AsyncLocal variable when WindsorServiceProviderFactoryBase was first creatd. The problem arise with kestrel or orleans in .NET 8, they use a Thread Pool that runs code outside AsyncLocal so it will break resolution. It was not possible to reproduce locally, but it was reproduced with production code. A repro for the bug still missing. Also we can support using a Global root scope only if we use only ONE CONTAINER in the .NET core DI, because basic structure does not allow to find the container that is resolving scoped component thus we cannot determin the right root context. Still work to do to support multiple container.
Configuration menu - View commit details
-
Copy full SHA for 1830955 - Browse repository at this point
Copy the full SHA 1830955View commit details
Commits on Feb 18, 2024
-
Added logic to support multiple container in .NET 8 DI
Needed to modify basic Castle.Winsor library to support the ability from IHandler interface to get the current kernel associated with the handler. This is needed to find the correct root scope associated with that kernel instance.
Configuration menu - View commit details
-
Copy full SHA for 7437a7c - Browse repository at this point
Copy the full SHA 7437a7cView commit details
Commits on Mar 11, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 36bbbf1 - Browse repository at this point
Copy the full SHA 36bbbf1View commit details
Commits on May 22, 2024
-
Updated nuget test adapter fixed a resolution bug
The bug happened when you register a service with one NON keyed component then again with KEYED components. The adapter incorrectly checked only the first returned service for KEYED and returns null. Identified after update to Orleans 8.1.0
Configuration menu - View commit details
-
Copy full SHA for 17d1010 - Browse repository at this point
Copy the full SHA 17d1010View commit details
Commits on Jun 24, 2024
-
Fixed IsDefault() usage in DependencyInjectionAdapter
If multiple concrete classes are registered in castle, when you resolve castle resolves the first one. With Microsoft DI is the oposite, you want the last registered. The resolution is now fixed to honor IsDefault() because previous code registered every component with IsDefault() if it is registered from the adapter.
Configuration menu - View commit details
-
Copy full SHA for 9499d3a - Browse repository at this point
Copy the full SHA 9499d3aView commit details
Commits on Jun 25, 2024
-
Fixed (again) resolution rules during resolve.
We added a new concept, an extendede property that allows the code to understand if the dependency was registered through the adapter (ServiceCollection) or directly through the Container. This allows us to change the resolution rule in case of multiple services registered with the same name.
Configuration menu - View commit details
-
Copy full SHA for b71829c - Browse repository at this point
Copy the full SHA b71829cView commit details
Commits on Jul 11, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 495fc21 - Browse repository at this point
Copy the full SHA 495fc21View commit details