When to use asp.net?

[Terry]

I had a discussion with a coworker of mine about whether a project should be
developed as an ASP.net app or as a VB.Net client app.

If the user needs to work off-line, then it should be a client app,
but other than that, what are the advantages/disadvantages of developing an
ASP.net app versus a VB.net client app.

Terry

[Onur Bozkurt]

Re: When to use asp.net?

In my opinion the first difference is in an asp.net application you don't
have to worry about your clients. What they just need is a web-browser.
Operating system, or its version is not important.

"Terry" <terry@xxx.co m> wrote in message
news:%236FbSIuf EHA.396@TK2MSFT NGP12.phx.gbl.. .[color=blue]
> I had a discussion with a coworker of mine about whether a project should[/color]
be[color=blue]
> developed as an ASP.net app or as a VB.Net client app.
>
> If the user needs to work off-line, then it should be a client app,
> but other than that, what are the advantages/disadvantages of developing[/color]
an[color=blue]
> ASP.net app versus a VB.net client app.
>
> Terry
>
>[/color]

[darrel]

Re: When to use asp.net?

> In my opinion the first difference is in an asp.net application you don't[color=blue]
> have to worry about your clients. What they just need is a web-browser.[/color]

In theory. In practice, I've seen plenty of web apps that are actually
IE-PC-only apps...which seems to be pointless.

That said, the one argument I've heard is simply delivery of the front-end
interface. If you use a client app, it my require installation on each
individual computer, which can be a nightmare for an IT department at a
large organization. (granted that *is* their job, but hey, whadya do). The
use of the web browser, even if it is just IE/PC is to circumvent the need
for any software installation on the desk machine.

-Darrel

[Alvin Bruney [MVP]]

Re: When to use asp.net?

it boils down to who owns the desktop. if you have control over the desktop,
you should consider developing a windows client because it is faster than a
web application (all things considered). if you do not own the desktop, a
web browser application should be the way forward.

usually, when you own the desktop, updates and installations are not an
issue. keeping your client current is also not an issue since you can
implement code to drizzle client updates so that they are always up to date.

An asp.net web application does not solve the problem of updates since you
have no way of enforcing an update policy for security patches etc. You
still need to code vigilantly for this.

--
Regards,
Alvin Bruney
[ASP.NET MVP http://mvp.support.microsoft.com/default.aspx]
Got tidbits? Get it here... http://tinyurl.com/27cok
"darrel" <notreal@hotmai l.com> wrote in message
news:egJe77ufEH A.3556@TK2MSFTN GP12.phx.gbl...[color=blue][color=green]
>> In my opinion the first difference is in an asp.net application you don't
>> have to worry about your clients. What they just need is a web-browser.[/color]
>
> In theory. In practice, I've seen plenty of web apps that are actually
> IE-PC-only apps...which seems to be pointless.
>
> That said, the one argument I've heard is simply delivery of the front-end
> interface. If you use a client app, it my require installation on each
> individual computer, which can be a nightmare for an IT department at a
> large organization. (granted that *is* their job, but hey, whadya do). The
> use of the web browser, even if it is just IE/PC is to circumvent the need
> for any software installation on the desk machine.
>
> -Darrel
>
>[/color]