Thin Client VB.NET Application - 3 tier architecture

Dear Experts,

I need to develop a thin client application in VB.NET.
This is what I mean by thin client - I need to provide a user interface ( probably developed in VB.NET) for our users. With this, I want to separate all the processing/logic and the database related access so that this all happens at our server and the user interface is thin.

I am not sure how to go about this implementation and deployment of these kind of applications.
Should I develop application with three tier architecture in VB.Net? If so how can I provide just the UI to the users and retain the database layer and the business layer at our server

Any sample examples or website links will be of great help.

Thank You in advance
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

To create the three tier architecture you would want to of course have the database tier, then create a web service for the business layer, and third a web site for the user interface.

If your not sure how to create or call a web service this video should give you a basic understanding.
Jeff CertainCommented:
Web services aren't the only option for the business layer. In fact, if you're planning on controlling both ends of the pipe, I'd strongly recommend using a WCF service with net.tcp bindings for performance reasons.

It also depends on your choice of UI technology. A web application is about as thin as you can get, but these have some issues -- like needing validation logic on the client side, and generally having to write that in javascript, while your server-side validation is in .NET. Silverlight eases this pain a little bit, but introduces a whole bunch of other issues.

However, if you require a great-looking UI, you're likely looking at Silverlight, WCF or an ASP.NET pages. WinForms are so last decade.

You're going to end up with two (or more) deployment packages -- one for the client and one (or more) for the various server-side pieces.

When architecting your services, be sure that you use chunky interfaces. One of the worst things you can do for performance and scalability is have frequent, small calls to your services. You want a coarse-grained API exposed to the client, so that significant tasks are performed with a single service call.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.