Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m working on a new project now, and have given some thought to the IoC setup. I’m aware that you shouldn’t be depending on the service location pattern (much, anyway), but that there are just a few places in a well-structured application where it may be necessary. In that case, do you use the CommonServiceLocator project, or not bother with it?
I’m essentially looking for feedback on whether the CSL is used at all, or how widely it is used.
Going purely on the number of recorded downloads here: Common Service Locator Downloads it looks like it has a very small number of users for a general purpose library.
It provides a level of indirection between client code and its service locator. The deal is that you sacrifice access to the APIs of your chosen IoC framework in return for portability across IoC frameworks. Unless your code needs to support multiple service locators, then it doesn’t really help you. See: When would you use the Common Service Locator.
Version 1.0 looks like a very basic factory pattern implementation, so it’s probably not worth worrying about too much either way.