Discussion on deprecated APIs for removal in future versions

The community needs to discuss what obsolete public public API’s can be removed for Windsor V5, including anything that might no longer be useful or could be replaced with something from the framework.

Anything that is identified as “generally agreed” will be dealt with in a PR which should be linked here.

Below are a list of obsolescent items found and their current status.

• Logging Facility: LoggerImplementation enum and the loggingApi XML property

• XML config in general (Not a thing for v5, @fir3pho3nixx)

• Parent/Child containers (Still in flight, @fir3pho3nixx)

• Burden Tracking (Still in flight, @hconceicao)

• IEnvironmentInfo (Still in flight, @jonnii)

• Deprecating Resolve(Type, IDictionary) in favor of IReadOnlyDictionary<string, object> (Still in flight, @jnm2)

• Obsolescense in general (Generally agreed)

• ActAs

• Parameters

• ServiceOverrides

• Properties

• BasedOn’T

• Where

• CustomLifestyleAttribute

• NoTrackingReleasePolicy

• AllTypes && AllTypesOf

• DefaultKernel_ObsoleteAPI

• WindsorContainer_ObsoleteAPI

[jonorossi]

@thuannguy I’d strongly recommend watching the Windsor repo on GitHub and participating in discussions including reviewing pull requests to ensure you like the direction of the project. It is an extremely low traffic project at the moment and the only way to make sure you voice is heard is to be involved.

[phillip-haydon]

Will sort a PR out tomorrow 😄 already turned computer off for the night.