CommonServiceLocator

Bouldraak's comment is spot on, however, I would note that CSL makes it's possible to use DI containers whether or not the dependencies being placed in the container are DI aware, thus, there is no need to rely on coding conventions as @junglemole ... [More] notes "is first and foremost good design by itself" (while that may be true, what we've seen over the last 30 years are systems which rarely make good design first and foremost. on the contrary, we often wish original authors had adopted interfaces and used a factor, or DI container and an IServiceLocator adapter.) [Less]

I've just been given time to update the libraries used in our product. I'm moving from version 1.1 to 1.3 but when I try to just perform a straight upgrade via Nuget I get the following exception. An unhandled exception of type ... [More] 'System.Reflection.ReflectionTypeLoadException' occurred in mscorlib.dll Additional information: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information. Can anyone suggest what might have changed between these releases to cause this or how I can get the LoaderExceptions? [Less]

I've just been given time to update the libraries used in our product. I'm moving from version 1.1 to 1.3 but when I try to just perform a straight upgrade via Nuget I get the following exception. An unhandled exception of type ... [More] 'System.Reflection.ReflectionTypeLoadException' occurred in mscorlib.dll Additional information: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information. Can anyone suggest what might have changed between these releases to cause this or how I can get the LoaderExceptions? [Less]

that's nowhere near a problem to design your system in a way it don't give a rubber duck about what IoC container you choose. your excuse is very weak and unconvincing. you are just resort to strawman here. dependency injection is not a container ... [More] , but a pattern. containers just implement it. and if you code is DI-ready (which is first and foremost good design by itself), you can use any IoC container without further investment in your own code. [Less]

that's nowhere near a problem to design your system in a way it don't give a rubber duck about what IoC container you choose. your excuse is very weak and unconvincing. you are just resort to strawman here. dependency injection is not a container ... [More] , but a pattern. containers just implement it. and if you code is DI-ready (which is first and foremost good design by itself), you can use any IoC container without further investment in your own code. [Less]

that's nowhere near a problem to design your system in a way it don't give a rubber duck about what IoC container you choose. your excuse is very weak and unconvincing. you are just resort to strawman here. dependency injection is not a container ... [More] , but a pattern. containers just implement it. and if you code is DI-ready (which is first and foremost good design by itself), you can use any IoC container without further investment in your own code. [Less]

that's nowhere near a problem to design your system in a way it don't give a rubber duck about what IoC container you choose. your excuse is very weak and unconvincing. you are just resort to strawman here. dependency injection is not a container ... [More] , but a pattern. containers just implement it. and if you code is DI-ready (which is first and foremost good design by itself), you can use any IoC container without further investment in your own code. [Less]

I have a problem that is very easy to replicate:* Create a Universal Windows app (for Windows 10).* In the package manifest, change default language to sv (Swedish, I assume other languages will work to).* Add a reference to ... [More] Microsoft.Practices.ServiceLocation.* Create App packages to be uploaded to the Windows Store.When the app is uploaded to the store, the store thinks that the app supports English. This is because of the Resx-file in the ServiceLocation project.My problem is that my app is a pure Swedish project and I can’t support English for various reasons (it doesn’t make sense in my case). Comments: Hi, This is a bug in VS15. See this blog post http://blog.galasoft.ch/posts/2015/12/solving-the-issue-where-unexpected-languages-appear-when-you-submit-to-the-windows-10-store-mvvmlight/ Laurent [Less]

I have a problem that is very easy to replicate:* Create a Universal Windows app (for Windows 10).* In the package manifest, change default language to sv (Swedish, I assume other languages will work to).* Add a reference to ... [More] Microsoft.Practices.ServiceLocation.* Create App packages to be uploaded to the Windows Store.When the app is uploaded to the store, the store thinks that the app supports English. This is because of the Resx-file in the ServiceLocation project.My problem is that my app is a pure Swedish project and I can’t support English for various reasons (it doesn’t make sense in my case). Comments: Hi, This is a bug in VS15. See this blog post http://blog.galasoft.ch/posts/2015/12/solving-the-issue-where-unexpected-languages-appear-when-you-submit-to-the-windows-10-store-mvvmlight/ Laurent [Less]

UUUUUGGGGGHHHHH and why isn't there any documentation for "properly registering a Unity Resolver" using this library???!?!?!?!? Come on guys, this is so freaking frustrating.