design question( the app is written in c# ;) )

[parez]

Layer A is on top on Layer B.
Layer A talks to layer B using the interfaces defined in B. For input
and return values.

My question is should i take out the interfaces from B and put it in a
separate project?

[Cowboy \(Gregory A. Beamer\)]

The extraction of interfaces is most useful if you are going to create a
completely different layer B for other applications. If you are simply going
to version with additional "providers", you can do that in the same library.
It really depends on where you are going with this one.

One time it is a great idea to move out into its own library is a case where
you have multiple clients who each need a slightly different version of the
library, but do not want to ship other client's implementations with the
library. You will generally go to a config driven provider model in this
case, however, so you can test multiple implementations with simple
configuration changes.

--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

*************************************************
| Think outside the box!
|
*************************************************
"parez" <ps*****@gmail.comwrote in message
news:53**********************************@d5g2000h sc.googlegroups.com...

>
Layer A is on top on Layer B.
Layer A talks to layer B using the interfaces defined in B. For input
and return values.

My question is should i take out the interfaces from B and put it in a
separate project?

[parez]

On Feb 28, 10:12 am, "Cowboy \(Gregory A. Beamer\)"
<[e-mail]:

The extraction of interfaces is most useful if you are going to create a
completely different layer B for other applications. If you are simply going
to version with additional "providers", you can do that in the same library.
It really depends on where you are going with this one.

One time it is a great idea to move out into its own library is a case where
you have multiple clients who each need a slightly different version of the
library, but do not want to ship other client's implementations with the
library. You will generally go to a config driven provider model in this
case, however, so you can test multiple implementations with simple
configuration changes.

--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

*************************************************
| Think outside the box!
|
*************************************************" parez" <[e-mail] in message

news:53**********************************@d5g2000h sc.googlegroups.com...

Layer A is on top on Layer B.
Layer A talks to layer B using the interfaces defined in B. For input
and return values.

My question is should i take out the interfaces from B and put it in a
separate project?

I am trying to make component B resusable and also replaceable if need
be.

1)If I use interfaces defined in B then it will make it resusable.
2)If i separate the interfaces in to a different project then it will
make B replacable by a component C which uses the same interafaces..
Correct me if i am wrong.

so 2 should be the way to go.