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

If you want to replace a complete component, then separation will work well.
If you can put things together in a single library, then it need not be (ie,
add classes). Plug and play is certainly easier if interafaces are in a
different project. For deploying, you might still wish to compile the
interface assembly into the other assembly when you get close to deploying.

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

*************************************************
| Think outside the box!
|
*************************************************
"parez" <psawant@xxxxxxxxx> wrote in message
news:dec6be63-5016-4b03-a19a-dd1a8fbd145b@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Feb 28, 10:12 am, "Cowboy \(Gregory A. Beamer\)"
<NoSpamMgbwo...@xxxxxxxxxxxxxxxxxx> wrote:
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"
<psaw...@xxxxxxxxx> wrote in message

news:53c3bd44-ebd0-4d82-a6cd-00b2c0d95211@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



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.


.

Relevant Pages

  • Re: Standard Ada Preprocessor (Was: why ada is so unpopular ?)
    ... The code is all legal Ada except that I have left out the thin C binding ... you need to partition the two as well as ... dependent is separate from the ... interfaces maintained as part of the project in common. ...
    (comp.lang.ada)
  • Re: Circular references not possible?
    ... > Idea of separating interfaces and having the rest of the app depend ... > separate project and localized the object creation to the factory. ... Yes they do;-) even without the Configuration Management application ...
    (microsoft.public.dotnet.languages.vb)
  • Re: [patch 2/6] [Network namespace] Network device sharing by view
    ... the device names so that each guest can have a separate ... Example as a prefix: guest0-eth0. ... be interesting to have the host also manage these interfaces ... and creates separate sockets bound to IP addresses of each device, ...
    (Linux-Kernel)
  • Re: creaping coupling......
    ... is coupled to B. Make C coupled to IB, which also indirectly couples it ... be compiled separate from them, tested separate from them, and used ... Put your interfaces close to the classes that use them. ...
    (comp.object)
  • Re: What would be a truly relational operating system ?
    ... lower physical layer (I mean on current disks, RAM, and CPU ... One perhaps tangential problem is that mainstream OS designers aren't really into making coherent interfaces, let alone applying information theory, even though some of them jabber about that. ... I had to cope with an IBM mainframe OS called MVS. ...
    (comp.databases.theory)
Quantcast