Skip to content
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

Custom controls are not auto-registered to and resolved by Windsor Container #4

Closed
jirikanda opened this issue Feb 12, 2019 · 1 comment
Assignees
Milestone

Comments

@jirikanda
Copy link
Contributor

Custom controls (direct descendants of Control, not UserControl) are not auto-registered to and resolved by Windsor Container.

@jirikanda jirikanda self-assigned this Feb 12, 2019
@jirikanda jirikanda added this to the 1.8.8 milestone Feb 12, 2019
@jirikanda
Copy link
Contributor Author

jirikanda commented Feb 12, 2019

After discussion:

  • 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!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant