No-Touch Deployment vs. ASP.NET
Why should I use No-Touch Deployment since there is
ASP.NET?
There is a bunch of reasons why you would choose a
Windows Forms application rather than a web application.
However if you need to create an OS-independent software
you will have to stick to ASP.NET.
ASP.NET is great and it will get even better in future
versions, but it also has it limits. With ASP.NET the
client is the Browser and Browser are “stupid”, because
they just display what is described in a meta language –
such as HTML. As a developer you have to ability to do
client processing using a script language like Jscript
which is unmanaged – and therefore potentially unsafe as
you can see from the amount of security updates
released.
When you need cutting-edge performance, want to use of
the local resources efficiently (e.g. DirectX), want to
integrate with local applications / APIs a “rich” GUI
with a high responsiveness (no postbacks to the server),
ASP.NET is simple the wrong choice.
And if you decide to create a Windows Forms application
it should not fail due to the complex deployment such
applications typically involve. This is exactly the
vision of No-Touch Deployment: Deploy your Windows Forms
applications as simple as Web applications.
|
|