Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / March 2005

Tip: Looking for answers? Try searching our database.

ADO.NET and Webservices

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Himanshu - 27 Mar 2005 15:27 GMT
Hello,

I'm trying to build a webservices 'application' that basically allows
any sort of client to plug-in and do do updates to the database
through ADO.NET (ODBC)

So generally like this,

[ CLIENT APP ]  <------> [ WEB SERVICES ] <-----> [ ADO.NET ]

Would anyone know of any links ... that give recommended strategies on
best practices, etc... to build those components.....

I've got the database structure, but a bit lost on how to best model
the webservices so that the client app can properly do
add/remove/updates.... and also allow synchronisation between
different clients.

Would really appreciate on any pointers in this area :)

Cheers,

Himanshu
MB - 28 Mar 2005 01:03 GMT
have you tried www.microsoft.com/practices ?

Mark.

> Hello,
>
[quoted text clipped - 19 lines]
>
> Himanshu

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.