Thanks Rainier,
I'll continue to read those patterns and see whether it seems reasonable to
apply them to my projects.
At first sight it seems the UIP Application Block is a little too complex
and instead of easing things for developing both versions, could end up
introducing more compexity on them. I know it could be better on the long
run, because of maintenance advantages, but, with the time constraint, I
don´t know if there is time for the learning curve associated with its
implementation.
David.
"Rainier [MCT]" wrote:
[color=blue]
> Hi David,
>
> Sorry I didn't read your question good enough, you already read the user
> interface application block.
>
> Let me think, if you need more information for your application architecture.
> You can keep on reading ofcourse there is a good book that explains patterns
> If you read it completly you will understand the Model View Controller
> pattern also (It's the last pattern in the book). Head first design patterns
> (Java book).
> And you can ofcourse hire a good consultant to get the project underway, try
> Microsoft consultancy services. Let them take a look at your design papers,
> this is a verry educational experiance.
>
> Bye,
>
> --
> Rainier van Slingerlandt
> (Freelance trainer/consultant/developer)
>
www.slingerlandt.com
>
>
> "Rainier [MCT]" wrote:
>[color=green]
> > Yes there is a best approach fro developing in these kinds of situations.
> > Use the Model View Controller pattern. This basicly means that you should
> > keep your data your interface and the logic seperated.
> >
> > Microsoft has a user interface application block which is probably overkill
> > but the pdf that is included in this block does explain the thought behind
> > the code.
> >
> > It's good reading material.
> >
> > Bye,
> > --
> > Rainier van Slingerlandt
> > (Freelance trainer/consultant/developer)
> >
www.slingerlandt.com
> >
> >
> > "David Pinx" wrote:
> >[color=darkred]
> > > 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?
> > >[/color][/color][/color]
