Thank you for all the replies.
The differences that I saw were:
- windows applications (desktop) need to be installed on each client's PC,
together with .NET Framework; changes determine a new installation on all
stations
- web applications install only on the web server together with the
framework; the clients access the app from a single location; any change
doesn't need to be installed on each station.
- web applications have the authentication/authorization mechanism partially
built
- desktop applications (windows forms) need the entire mechanism built
- web apps have validation controls
- windows apps don't have validation controls, data needs to be validated
through code
please add more differences if you know
Daniela,
Where did you read the conclusion you wrote in this thread, because non of
these points is true and even most are in contrary?.
> - windows applications (desktop) need to be installed on each client's PC,
> together with .NET Framework; changes determine a new installation on all
> stations
As it is Net they both have to be installed once on a webserver using
Publish. If it is not a Net application than the Net is not needed to be
installed. At IE7 this last point is even gone ofcourse.
> - web applications install only on the web server together with the
> framework; the clients access the app from a single location; any change
> doesn't need to be installed on each station.
Even this is not true, if you are using JavaApplets, javascript, activeX or
whatever, you have to be sure that the right version is in the users cache..
> - web applications have the authentication/authorization mechanism
> partially built
> - desktop applications (windows forms) need the entire mechanism built
With a windows application you can easily use the Is In Role
authentication/authorization mechanisme as in any windows application.
> - web apps have validation controls
> - windows apps don't have validation controls, data needs to be validated
> through code
The validation on Web is fair, you cannot simple check a date by instance if
that is not typed in the way it is given on the webpage. In a window forms
application a lot is done for you, just as the user is typing it.
Cor
Daniela Roman - 15 Oct 2006 17:05 GMT
I was referring to .NET environment exclusively and this was my
understanding reading different sources, it's not necessarily true, I just
wanted to confirm.
In a multi-user environment a web application doesn't need to be installed
on each client's computer like with desktop apps., where there is only one
installation on the web server
A change in the app will determine one single re-installation on the web
server but in the desktop case, it should be done on each individual PC
.NET Framework needs to be installed on either WEB server (for web apps) or
on each PC (for desktop) for .NET apps to run, which is a one-many relation
> Daniela,
>
[quoted text clipped - 33 lines]
>
> Cor
Cor Ligthert [MVP] - 15 Oct 2006 18:00 GMT
Daniela,
Try either in a web or in a windowforms application using the C# 2005 IDE
Build
Publish
Cor
>I was referring to .NET environment exclusively and this was my
>understanding reading different sources, it's not necessarily true, I just
[quoted text clipped - 45 lines]
>>
>> Cor
Steven Nagy - 15 Oct 2006 23:58 GMT
Yes Daniela you are right.
As an overall guidance, the process of updating those seperate
instances is as easy as each other, but the overall concept is correct.
If you are building web app, you only need to update the app on the web
server. If you want to update a deployed windows app, you need to
udpate the individual applications on each pc. There are easy ways to
do this and VS2005 has one click deployment methods, but the overall
result is still the same.
Naturally there are lots of other factors such as how much control you
have over the target windows apps, if they use a shared or standalone
database, etc.
I guess if you plan on doing lots of updates, web is the way to go. But
if you want the improved integration with the windows api, then use a
windows app.
<answer flame="false">
The amount of crap that runs client side now days pretty much makes the
concept of a "thin client" redundant anyway, in my opinion.
</answer>
Cor Ligthert [MVP] - 16 Oct 2006 05:37 GMT
Steven,
I think that you are beside the true situation and still are using facts
which seemed to be true in the previous century. The (in my opinion) most
important choice you have to make is if your supposed users will download
your application on their computer.
If that is not the fact, than a webapplication is the only way to go. In
other words, do the users belong to your domain or do they want to belong to
that.
Cor
> Yes Daniela you are right.
> As an overall guidance, the process of updating those seperate
[quoted text clipped - 19 lines]
>
> </answer>
Steven Nagy - 16 Oct 2006 05:48 GMT
> I think that you are beside the true situation and still are using facts
> which seemed to be true in the previous century.
Which facts do you think were true in the previous century?
Are you implying that those same facts are no longer valid in this
century?