I hope this is both the correct forum, and that maybe someone can offer some information on my question.
I've been building up a series of libraries that are used within the applications we develop at work, I've worked hard to separate them based on the following structure:
- UI (typically the web based application)
- Business (the entities, Patient, Ward, Hospital etc)
- DataAccess (a set of DataServices which get/set data to the data source)
- DataSource (typically SQL server)
The problem I initially encountered was that I was creating say the following;
for an application, and more often than not we would also need a web service. The web service had its own little set of files for handling the getting/setting of the data.
To me this felt wrong. Surely if I have a DataAccess library specifically for the getting/setting of data which resides in between the Business and DataSource layers I should make every attempt to use it for the WebService too - why re-invent the wheel etc?
Without going into all the detail, the structure of these services were almost identical, aside from one made calls to stored procedures, and one made calls to web services. I took each
View Complete Post