What dependency injection framework do you use with Csla? #3265
Replies: 4 comments 5 replies
-
I'm interested in this as well. I use the built-in capabilities, but have colleagues who really like Autofac a lot. Within the context of CSLA itself, as you might imagine we only use the capabilities provided by |
Beta Was this translation helpful? Give feedback.
-
I came from the WPF and used dependency injection with PRISM. At that time, I was using Unity (another MS ejected tech) that became obsolete and is no longer supported by either MS or the community. PRISM I feel is going to go the same way. I have since limited myself to one external tool and that's Automapper. I use MS's dependency injection because I have no desire to wake up (again) and find out the framework is no longer supported. It's bad enough that geospatial support is through an addon and not imbedded with .NET. I think autofac has been around so long that is could be a viable alternative, but I'm too busy to learn another framework and have been burned too many times. |
Beta Was this translation helpful? Give feedback.
-
We are currently using Unity, but given that's no longer supported we'll eventually move to the MS DI extensions. |
Beta Was this translation helpful? Give feedback.
-
I use out-of-the-box solutions as they are supported longer and tend to incorporate the useful features of the trendy packages eventually. I started looking into AutoFac because of a desire to build a plugin/modular-based solution. I recently found a project called Octane that is already plugin/module-based. Octane looks to be created by the same people who created DotNetNuke from years past. |
Beta Was this translation helpful? Give feedback.
-
I am interested to know what fellow Csla developers are using for Dependency Injection.
12 votes ·
Beta Was this translation helpful? Give feedback.
All reactions