I am going lead a project, where I have Asp.Net webapp with SQL Server 2008 database and a WCF Service with REST to expose the data of the database to clients like winform app, java apps, android apps etc.
I want to use LINQ to Sql in my project. Earlier i have experience over the n layered architecture. Please help. How to take steps?
I have 4 different projects in a single solution. Should I need to divide it parts like WebApp with Sql Server database in a single project, Service and Client in two differents projects, as we might deploy our WCF service in some other server…
**See update
to make it more clear , my project has three main aspects, a web app, service and client app. WebApp will be hosted on someserver. On the same server, i would like to deploy the service. Webapp has nothing to do with the service. It will directly interact with the database. On the other hand, the service has permission for selecting records from the database, not Insert, delete and update. Client app will be scattered to different location. It might be a winapp, wince app ,android app or java app. and it will interact with the service to fetch data only. Thats my plan.**
If your asking about how to architect a good n-tier application I would suggest you quickly read http://www.amazon.co.uk/Professional-Enterprise-NET-Wrox-Programmer/dp/0470447613
Really, it all depends on your requirements. I would generally have my WCF project separate from the ASP.NET project so that ‘heavy’ processing tasks can be passed to the WCF and not degrade the websites performance.
n-tier has been the de-facto design for years, but for smaller projects people are arguing that EF + n-tier etc, is overkill and that micro-frameworks like NancyFx and Simple.Data are more appropriate. It all depends on what you are actually building.
Or are you asking how to get started with Linq?
Mannings “Link in Action” is very good. As are the webcasts on http://shop.tekpub.com/products/linq