4 ms·
I can attest to how well designed Autofac is. I had to decide on which DI framework to use on a small front end WPF application that I worked on at a job last
by alimbada 10y ago
I can attest to how well designed Autofac is.
I had to decide on which DI framework to use on a small front end WPF application that I worked on at a job last year (the app had a lot of singleton classes that were impossible to unit test hence why I needed to introduce a DI framework). I'd come from a job where larger framework choices had been made years prior by senior developers and their framework of choice at the time was Microsoft's Unity so that was what I had worked with for ~5 years. After a week or so of research and deliberation I decided to go with Autofac and found it to be really easy to set up and use. For me it hit the sweet spot between built in functionality and performance.
- xorxornop 10y agoAnd I, too! After discovering Autofac, I've not looked back. Before, I'd tried various DI frameworks, and always left thinking "I totally do not get what why people like this DI stuff". Then, Autofac. Everything just works. But - it's also powerful enough that if I need to do something really clever and/or complex, I can, and it invariably works. It works just as well in Core. As such, it's usually the first package I install in a new Core project.
- flukus 10y agoI love autofac, I've been using it for a decade, but have you run into any situations where the DI built into .net core didn't cut it? In my (limited) uses I haven't found any shortcomings so far.