client/server implementation

[Chris Bordeman]

Hi all. I need to create an app that runs both at individual client PCs, on
the client's on-site server, and on a main server depending on network
connectivity, probably w/ database replication.

What technologies should I use so that the software running on all three
locations looks the same, scales from the single PC to the site server, to a
master off-site server, WITHOUT writing different software for each "tier?"
Moreover, the # of tiers could increase.

I'm guessing WPF and SQL Express / Server to start...

 

[Michael Nemtsev, MVP]

Hello Chris,

You forgot the WCF, which provide abstraction layer between presentation
and data.
It's that clue which helpÙ you to make physical data location really transparent

---
WBR,
Michael Nemtsev [.NET/C# MVP] :: blog: http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo


CB> Hi all. I need to create an app that runs both at individual client
CB> PCs, on the client's on-site server, and on a main server depending
CB> on network connectivity, probably w/ database replication.
CB>
CB> What technologies should I use so that the software running on all
CB> three locations looks the same, scales from the single PC to the
CB> site server, to a master off-site server, WITHOUT writing different
CB> software for each "tier?" Moreover, the # of tiers could increase.
CB>
CB> I'm guessing WPF and SQL Express / Server to start...
CB>

 

[sloan]

You need WCF.

It is an abstract model, that puts you "above" any one communication
methodology.

I suggest Juval Lowry's book on programming WCF services.




"Chris Bordeman"