C#/ASP.NET apps vs. Linux multi-user desktop application

[Eugene Zilberleyb]

I have a web-based bussines application written in C#/ASP.NET

Recently my boss start pushing to re-write the app as Linux multi-user
desktop application. In his design users will need to connect to Linux server
via VNC or alike to use the app.

I am not familiar with this kind of application design. I'd appretiate any
help explainig pros and cons of this approach vs. web and perhaps vs.
traditional client-server design

Thank you

[Marvin Landman]

Decades age when there were no PCs mainframes with terminals used to be
the only possible solution.

Nowadays every single person tends to have at least one computer.

I don't see a single advantage of using the server as a
telnet/VNC/remote desktop server if you can accomplish the same using a
client application.

Web applications are good because you don't have to install or download
anything.

On the other hand I don't like web pages that are in fact desktop
applications.

Windows Update "web site" or Remote Desktop "Web" Connection are good
examples of abusing the browser to run desktop applications packages as
ActiveX components. Starting with Vista Windows Update is a real desktop
that is the right solution.

Outlook Web Access on the other hand is a good example of what a real
web application is.

If you ASP.NET web application really is a web application rather than a
host for client applications (ActiveX, Java, .NET, etc.) then I don't
see a reason to rewrite.

If your application massively depends on client components you may want
to consider rewriting the "web" application as a desktop application.

Running the same application on the server and accessing via VNC is just
wasting of computer resources. You will need to buy more servers while
workstations will have spare resources that could run the same
application on the client computer without needing more resources on the
server.

Marvin