Just as any other application, be aware that when is spoken about a n-tier
environment in Windows is not a true n-tier, however just a multi-layer
solution.
This means that you split your application in more projects, most often done
in the way as UI, business rules, data access.
However the latter is more and more discutable, because in fact it has not
so many advantages in Net (more disadvantages). Probably you can split it
better up functional.
(Although I always will keep my UI interfaces apart from the others).
.... not least of which because very few Patients are marked as being
<Serializable()>, effectively ruling out any solution that relies on
..Net Remoting or W.C.F. shoving them through a length of wire from
computer to computer.
Ouch!
More seriously, though, you'll be looking at something like ...
(1) back-end Database,
(2) [maybe] "entity" layer (to clean up the inevitable "mess" that is
the database),
(3) "business" layer, that actually "does" things, and
(4) the User interface on the front.
Bear in mind that any (or all) of the layers may change at /any/ time.
HTH (but knowing full-well that it probably /doesn't/)
Phill W.
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.