Just upgraded Castle to 3.2 (from 3.1) and noticed lots of DependencyResolverException with stack traces in Debug output. If anything else, this slows down our main installer as it takes now ~20 seconds to run (instead 1 second before) when application is launched under VS' Debugger.
The setup: - An IStartable component that has a dependency - That dependency is registered much later in time So, after each component registration Castle tries to check if our IStartable has it's dependencies. If it fails, it puts an exception in Debug window until later the dependency is registered. The workaround is evident, move the registration of dependency before IStartable component. But I wanted to ask if this behavior really changed in 3.2 and it's not something that should be added to issue tracker... Thanks, Valeriu Caraulean -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/castle-project-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
