WindowsForms or ASP.Net

[Mike Lopez]

Hello.

For an Intranet application, what would be some reasons to use ASP.Net and
NOT use WindowsForms?

I can't think of any.

Thanks in advance,

Mike

 

[Eliyahu Goldin]

Mike,

If the development team has necessary experience, I would recommend making
it in asp.net.

The reasons:

No client installation.
Browser-based GUI often looks better than windows-based one. You can use css
filters, flash, other things that are not so easy available in windows.
Server-based architecture, much easier to maintain.
Sooner or later someone will want to run the application from the web.

Waiting to see more reasons.

Eliyahu

 

[Guest]

Morning,

Have you checked out Smart clients??

1] No client installation. =
Is auto thru the Browser. All user sees if a small loadtime when newer
version
needs to be downloaded. Break up app into small pieces and this is cut
down
too.
2] Browser-based GUI often looks better than windows-based one. You can use
css filters, flash, other things that are not so easy available in
windows.
Usually in a Internel app all this flash is looked down on by upper
mgt. And
the GUI is faster then any web GUI. Plus the Windows controls are much more
feature rich.

 

[Steve C. Orr [MVP, MCSD]]

ASP.NET apps tend to be much easier to deploy, and they don't tend to have
issues with firewalls in case you have some users on the road. Some users
also find web browsers comforting.
If those issues aren't a big deal to you, then Windows Forms sounds like a
good solution for a rich client application.

 

[Guest]

Smart clients still need install .NET framework on client machine.

Browser-based app is slowly. Windows app is fast and powerful.

 

[Eliyahu Goldin]

Browser-based app is slowly. Windows app is fast and powerful.

A thick client windows application can be slower then a server-based one.

Eliyahu