We do this very successfully by using Web Services. We have a rich but thin
client that consumes the services, AJAX code that consumes them and gives
you field-at-a-time processing in a browser and ASP.NET pages that
consolidate a pages worth of data and submit it. As a bonus, the .NET
Compact Framework gives us a PDA client which we are using on devices like
the O2 XDA II. The services are quite generic - there are only a few, but
one of the parameters is an XML document which contains a description of the
request (eg <Field name="CustomerAddress" value="123 Some St"/>) and the
response is an XML document which contains the sum of the changes the server
has made based on business rules executed. In fact, as another bonus, its
B2B ready and fits in well with SOA.
Note this is a home-baked solution- we dont use much (any?) of the MS
provided architectural stuff.
Radek
"David Pinx" <Da*******@discussions.microsoft.com> wrote in message
news:56**********************************@microsof t.com...
Greetings,
I will be developing an application that will have two versions, a web
application to be deployed at the client side and a windows application.
The question is, what would be the best approach for developing these two
versions reusing code as much as possible?. Is there a best practice for
this
type of development?
I have read about User Interface Application Block, but I don't know at
this
point if that is a good fit.
Any comments, suggestions?