You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Auto-registering custom controls is not the best practice.
But it is usefull.
There is no abstraction in custom controls.
We decided to auto-register controls which do not have public parameterless constructor.
Controls with public parameterless constructor (for LiteralControls, Labels, ...) are not registered to Windsor Container and instances are created by Activator (because of performance).
Castle Windsor (Resolve+Release) is ~4x slower when compared to Activator on a class with parameterless constructor (which is still very very good!)
Custom controls (direct descendants of Control, not UserControl) are not auto-registered to and resolved by Windsor Container.
The text was updated successfully, but these errors were encountered: