Windows Vista is Microsoft's latest Operating System.
For development of applications on Vista, although you can use
WinForms, the new technology is Xaml. It is not so much an
architecture, as it is a development tool, i feel.
Designer support for creating Xaml apps is also some time away (it will
be integrated in the next version of Visual Studio). However, at this
time you can do your Xaml apps by hand.
Why you should care about Xaml is that on the Vista platform, the same
code (i.e. Xaml code) can be used to deploy your application as either
a webapp or a windows app.
And of course, Xaml (or rather Windows Presentation Framework) offers
you the ability to have a very much richer UI API, which in turn means
better looking apps.
Going back to the other two:
ASP.Net - yes, purely server with Xhtml on the client
Smart Client - yes, it would mean logic is on the client, and
communication with server can be through web services, remoting, or a
custom protocol.
A quick note, presence of .net 1.1 framework on client machines is not
a big deal. It is not really a barrier.
Also, once again, it really depends on your application scenario
whether you would want to chose a Smart Client vs a Web Application.
For example, if you wanted to provide an offline mode to your
application, then it may be better to go for a Smart Client...
- V
Avi wrote:
V thanks for answering!
Please clarify: Vista ans Xaml - are they a new "architecture" (as
opposed to specifying the user interface as XML which why should I care
about this, probably handled with tools anyhow)?
ASP: Work on the server, pure XHTML on the client
Smart Client: Work on the client using .Net, interact with the server
(using web services?)
Vista + Xaml???
If it's a new architecture, it might be worth getting into it if it's
stable.