|
-
Jul 3rd, 2008, 09:40 AM
#1
Thread Starter
Junior Member
[2008] Why WCF in N-tier?
-
Jul 3rd, 2008, 02:22 PM
#2
Re: [2008] Why WCF in N-tier?
Did you still want the question answered or did you post this in some other thread?
-
Jul 4th, 2008, 12:47 AM
#3
Thread Starter
Junior Member
Re: [2008] Why WCF in N-tier?
Yes I wish to have an answer, its a vb question but I accidentanly post it in here C#, but I cannot delete, so I posted it in VB.net section, anyway here's the question just in case:
I've watch video tutorials on vb 2008 N-tier applications and they teach the new method of separating the tableadapter and dataset while having wcf and then those contract stuffs, but what if I'm not hosting the tableadapter on the server, I just want my client app to connect to the database directly using its datalayer dlls. Im not needing any webservices or any sort of communications. Could I just go on without WCF? Its just a simple windows application that connects to a database that has stored procs and then edit-save. I'm planning on using Linq to sql. Any suggestion regarding a much better approach is appreciated. Thanks
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|