Re: Are ASP.NET user interfaces essentially dead now?

However, using winforms requires that the client has the .NET framework
installed. At this point that is a big leap to take.

Where as an ASP.NET app can work just fine on other browsers/platforms with
proper care by the developer, there is no way a developer can make winforms
work on a platform that does not have an implementation of the .NET
framework installed.

And yes, while the application in winforms will be secure, it may be to
secure. If the sandbox is too tight, the application may not be able to
make a web service call back to the web server for example. Now the user has
to go configure security on their machine - what average user is going to
know how to do that?

Another issue is someone checking their email or the news from a kiosk.
Those machines are locked down pretty tight - the odds of them being open
enough to run your winforms application? I don't know.

Personally, I don't see winforms as a viable option for web development for
the forseeable future. But that's me, I could be way off.

"Rob R. Ainscough" <robains@xxxxxxxxxxx> wrote in message
news:%23gqpHyB$FHA.140@xxxxxxxxxxxxxxxxxxxxxxx
> VS 2005 I have:
> ClickOnce deployment
> User's that hate and or don't want to use an IE Client (don't blame
> them)
>
> I don't see how ASPX web pages are going to survive? With .NET 2.0 and
> clickonce deployment my app is 427KB (even with modem dialup speed it
> doesn't take long to download) -- the user gets a very friendly secure
> WindowsForm app (most of them don't even notice they're not under IE
> anymore) that performs considerably faster than any ASP.NET app.
>
> The road map as I see it:
> IE client -- back to static just clickonce links that open up
> WindowsForms apps
> Vista -- .NET 2.0 built in (no need to download)
> WebServices -- called from WindowsForms apps (keeps it secure and
> firewall friendly)
> WindowsForms are a HELL of a lot more secure (no IE attached activex
> components, no data miners, click monitors, etc. etc.)
>
> The way I see it -- user interaction is going to move back to WindowsForms
> since the IE client by definition is just NOT user friendly, NOT
> programmer friendly, and has a ton of other issues surrounding it in terms
> of security and performance and flexibility.
>
> Don't get me wrong, web development will still exist (web services and
> basic static content), but I believe anyone doing serious business
> applications using the web will migrate to this approach -- it really is a
> win win.
>
>
>


.

Relevant Pages

  • WSE 2.0 Instant Notifications
    ... app on a client machine. ... i think this would be possible setting up a TCP listener on Client ... Machine Winforms Application. ... Maybe we can find out the IP address of the Client machine from Soap ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Are ASP.NET user interfaces essentially dead now?
    ... it will be tight enough that you can't call SQL ... takes longer to develop ASP.NET interface than a windowsform app ... And communicating with a Web Service is not required the ... > I see Winforms doing the major amount of interface work and leaving the ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Server did not recognize the value of HTTP Header SOAPAction
    ... I created a new test winforms project in 1.1. ... The test app works OK, ... I understand you've developed an ASP.NET webservice ... application is sending an unexpected SoapAction header to the service. ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: Are ASP.NET user interfaces essentially dead now?
    ... interactive interface work -- they are fundamentally not suited to get the ... (or whatever client you choose). ... based app interface, or I can spend 2 months for the same windowsforms based ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: Using kerberosSecurity Throws Security Exception
    ... I am experiencing this error while trying to use a Windows XP client ... application to access a web service located on a W2k3 server. ... client app on the server, ... > Account with a Custom Principal Name using SetSPN.exe utility. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)