You can call web services from any code that can execute an HTTP request,
with varying degrees of difficulty. Calling web services from Window forms
(or any .Net code) code is trivial, using the "add web reference" to point
your forms app to the web service wsdl. This generates local proxy classes
that should feel very natural to you if you have used DCOM proxies. Whether
you decide to use fat or thin clients is more of a deployment preference,
depending on what platforms your clients are on.
One example I can give you is my application is web based (asp.net) but it
calls a web service layer for all business logic. I then have some windows
forms utilities I wrote which also use that same web services layer.
Performance is really good, especially if you take advantage of caching in
web services. hope this helps.
"Ed Staffin" <an*******@discussions.microsoft.com> wrote in message
news:2c*****************************@phx.gbl...
Hi all,
I sent this the other day but got no responses, so, I
thought I would try again.
I am thinking about the next version of my application
(it's an accounting app) and it would seem that web
services might be quite useful. If I can get rid having to
create a web app, and instead can use a regular windows
app on the client, that would be fantastic. Can I look at
web services as a better DCOM? How is performance? Is this
just another way of running an activeX form inside a
browser without having to run it inside a browser? Have we
come full circle where we are going back to fat clients?
Are Web Services a way for me to have the richness and
control of a windows client with the flexibility of having
remote logic and data? Has anyone scrapped an existing web
app for a windows/webservice replacement?
Thanks ... Ed
Thanks ... Ed
