The correct way to implement database access using .net remote access

Question

I am trying to implement a .net remote access system where several clients need access to the server database. Client calls can be concurrent, but I want the queue of client requests to the database to avoid concurrent access to the database.

I just study .net remoting and read about single-user, singleton and client activated objects. Do any of these methods do what I want, or at least support what I want?

Also, should I use a remote .net network or is this a WCF path?

Yours faithfully

Ash

Answer 1

, WCF. , Remoting.

, , Entity Framework Linq to SQL Web-. !

: http://marcgravell.blogspot.com/2008/12/astoria-and-linq-to-sql-getting-started.html.

: , , , IIS . , web.config.

, ... WCF Data concurrency, , ? , .

, , , . .

Answer 2

.NET Remoting WCF. - .