WPF Data Access Layer Architecture

Question

I am currently developing a WPF client application that uses Linq-to-SQL for typed table objects and wraps many CRUD stored procedures in an MS SQL database on an external server. I do not foresee data manipulation directly through the context, only stored procedures.

My two biggest problems: 1) Database security 2) Flexible architecture

As far as I can tell, since the application will be available for download via the Internet, saving information about connecting to the database in the application itself is not an option (for security reasons). I feel that my only option is to put my DAL in a web service.

User credentials can be transferred together for each operation, and database connection information will be stored securely on a secure web server.

I am curious if this method is really valid, and if it is so optimal? Can I easily serialize Linq-to-SQL objects (table and stored procedure results) to send back and forth between the client and the web service?

Thanks in advance.

Answer 1

You are right, if your application is used over the Internet, you should pretty much place the middle tiers there.

CRUD, , ADO.Net Data Services. REST, .

ASP.Net( , ..), ( , ).

, .