If I wanted to keep my data in SQL Server, but users wanted to use a thick client WinForms application, So what will be the best practice way to call from database from WinForms? And how easy is it?
I think that I am trying to focus on the issues from this point of view and someone needs to go (a) with intermediate web services, or (b) Asp. Net or something else to go
I really have a simple app that requires a database and I will have only 10-30 customers connecting to the LAN / WAN network which will be connected.
Edit: So the focus of my question was regarding the communication protocol / approach in the database from the client PC, i.e. LAN / WAN
If you have PC and DB server closed, its simplest solution is to use direct link-to-SQL approaches - there is no additional WCF service level in between this kind of service Layer is an important quantity The complexity combines.
If you want to go that route (possibly due to your van clients), then I suggest you see a layer above the bare WCF. This is probably the easiest and fastest way (such as your Linq-to-SQL or Entity Framework model) to expose the data model as a RS feed for the WAN / Internet client.
The WCF is actually one big beast and scares many people in this way - but you do not need to know about each set and knob to use it. For some aspects of WCF, I advise those two episodes that Dotnet Rocks TV - Excellent Identity Content:
Comments
Post a Comment