dephi background.
> > It took me a while but finally I got them doing unit testing, but still
> not
> > as much as I would like.
> > Today I also tried to convince them(the development manager) to
> > use dependency injection but he said it was over complicating things and
gt; developers aren't alt.net type. They're older and just love their RAD, User
> Controls, coming from a dephi background.
> It took me a while but finally I got them doing unit testing, but still not
> as much as I would like.
> Today I also tried to convince them(the dev
--
> *From: * mike smith
> *Sender: * ozdotnet-boun...@ozdotnet.com
> *Date: *Thu, 27 Oct 2011 16:46:45 +1100
> *To: *ozDotNet
> *ReplyTo: * ozDotNet
> *Subject: *Re: Other developers don't like dependency injection
>
> On Thu, Oct 27, 2011 at 3:00 PM, Nathan Schultz
:46:45
To: ozDotNet
Reply-To: ozDotNet
Subject: Re: Other developers don't like dependency injection
On Thu, Oct 27, 2011 at 3:00 PM, Nathan Schultz wrote:
> I'd probably sell it differently.
>
> Instead of saying you "don't know" where the objects come fro
ast some of the "old hats" here I temporarily changed
> terminology. Dependency Injection (let alone IoC) would draw blank looks,
> but say "plug-in system", and they've all rolled one before and are
> comfortable with the concept.
>
>
>
Also, it sounds
issenters:
>
> Black hat on :
>
> How can you say that dependency injection (I’m not taking on the whole
> inversion of control pattern, but I might. Jury’s still out on that one.)
> creates loosely coupled units that can be reused easily when the whole point
> of DI is to require the ca
ystems (and they nearly all do) I'd introduce DI at those locations and use
the excuse "it allows us to test OUR application without testing that
external system" and then start to work your way back into the core. Start
with "poor mans dependency injection" by
For a given class
Not wanting to start a flame war here, but DI has some dissenters:
Black hat on :
How can you say that dependency injection (I'm not
taking on the whole inversion of control pattern, but I might. Jury's
still out on that one.) creates loosely coupled units that can be reused
e
nance costs (modular design, easy to refactor, easy
to replace components, easier to extend, fewer system wide bugs, helps with
a cleaner implementation, less spaghetti code, etc).
To get it past some of the "old hats" here I temporarily changed
terminology. Dependency Injection (let alone Io
lder and just love their RAD, User
> Controls, coming from a dephi background.
> It took me a while but finally I got them doing unit testing, but still not
> as much as I would like.
> Today I also tried to convince them(the development manager) to
> use dependency injection but he s
No, you are not wrong.
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of Michael Ridland
Sent: Thursday, 27 October 2011 13:46
To: ozDotNet
Subject: Other developers don't like dependency injection
So I've been working with this client for a few
as I would like.
Today I also tried to convince them(the development manager) to
use dependency injection but he said it was over complicating things and
it's confusing because you didn't know where the object came from. I argued
for decoupling and that objects shouldn't need to know
wher
n Thu, Aug 5, 2010 at 7:56 PM, Maddin, Peter <
> peter.mad...@pathwest.wa.gov.au> wrote:
>
>> I am experimenting with Dependency Injection in the Microsoft CAB
>> framework.
>>
>>
>>
>> From http://blog.irm.se/blogs/home.aspx?App=eric&p=11
>
This article provides some options..
http://www.sqlservercentral.com/articles/T-SQL/61918/
<http://www.sqlservercentral.com/articles/T-SQL/61918/>
On Thu, Aug 5, 2010 at 7:56 PM, Maddin, Peter <
peter.mad...@pathwest.wa.gov.au> wrote:
> I am experimenting with Dependency I
cy on the View (the Passive View
pattern).
Dave
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of Maddin, Peter
Sent: Thursday, August 05, 2010 2:56 AM
To: ozdotnet@ozdotnet.com
Subject: Dependency Injection
I am experimenting with Dependency Injection i
> OIC
IOC - fat fingers
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of Nic Roche
Sent: Thursday, 5 August 2010 8:43 PM
To: 'ozDotNet'
Subject: RE: Dependency Injection
Hi Peter,
Sorry _not_ to address your issues directly.
Roche
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of Maddin, Peter
Sent: Thursday, 5 August 2010 7:56 PM
To: ozdotnet@ozdotnet.com
Subject: Dependency Injection
I am experimenting with Dependency Injection in the Microsoft CAB framework.
>F
I am experimenting with Dependency Injection in the Microsoft CAB framework.
>From http://blog.irm.se/blogs/home.aspx?App=eric&p=11
Who says
In this post I'm back covering the CreateNew attribute that you can use in a
class that is instantiated by
ObjectBuilder<http://www.co
don't need to. They can both just be separate dependencies.
Jeff
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of Michael Minutillo
Sent: Wednesday, 28 July 2010 8:22 PM
To: ozDotNet
Subject: Re: Dependency injection
Hi Jeff,
Most IoC conta
Hi Jeff,
Most IoC containers (Unity included) allows you to have two type-mappings
pointing to the same destination type. That means you could create a second
interface that is only about those low-level calls.
So you might have
interface IDataRepositoryA { Customer Load(int id); }
interface IDa
tnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of Jeff Sinclair
Sent: Wednesday, 28 July 2010 21:15
To: 'ozDotNet'
Subject: Dependency injection
Hi,
I am using Microsoft unity to do dependency inject but I have a small
problem.
Let's say I have a business layer
Hi,
I am using Microsoft unity to do dependency inject but I have a small
problem.
Let's say I have a business layer assembly and a data layer assembly. The
data layer exposes 2 interfaces,
IDataRepositortyA and IDataRepositoryB. These are both constructed by unity.
Now let's say IDataRe
22 matches
Mail list logo
