Agree with Nick here. Useful for testing mainly and haven’t found it annoying yet. We don’t bother with tiny apps when writing tests is a waste of time.
On Wed, 4 Dec 2019 at 10:34, Nick Randolph <n...@builttoroam.com> wrote: > I’m interested in the opinions regarding the use of DI – why is it that > you avoid it? > > > > I’m asking because I see cases where I find DI invaluable (eg testing) and > almost never find that it gets in the way. I’m interested to know whether > the opinions are generated based on bad experiences with DI, or a perceived > lack of benefits of DI. > > > > *Nick Randolph* | *Built to Roam Pty Ltd* | Co-Founder, Technical Lead | > +61 412 413 425 | 1300 613 140 | www.builttoroam.com > The information contained in this email is confidential. If you are not > the intended recipient, you may not disclose or use the information in this > email in any way. Built to Roam Pty Ltd does not guarantee the integrity of > any emails or attached files. The views or opinions expressed are the > author's own and may not reflect the views or opinions of Built to Roam Pty > Ltd. > > > > *From:* ozdotnet-boun...@ozdotnet.com <ozdotnet-boun...@ozdotnet.com> *On > Behalf Of *David Burstin > *Sent:* Wednesday, 4 December 2019 10:19 AM > *To:* ozDotNet <ozdotnet@ozdotnet.com> > *Subject:* Re: DI in MVC > > > > Yep. I avoid DI like the plague, but no option in a legacy ASP.net MVC > project. Thanks anyway. > > > > On Wed, 4 Dec 2019, 09:58 Greg Keogh, <gfke...@gmail.com> wrote: > > > > No takers? > > > > Sorry I can't help. I only use DI when I'm forced to, or it's really > simply integrated (like in Blazor). I consider DI another form of "magic > plumbing" and prefer something closer to the service locator pattern. The > problem you're seeing is one I hit when writing Xamarin with FreshMVVM, it > became DI spaghetti --* Greg K* > > > >
