Re: .NET

Abraham <abraham@xxxxxxxx> wrote:

> No you are not alone. I think the moment MS begins to use .NET for its
> Office suite, it's time to switch to .NET, and no it won't be too late
> because win32 apps will continue to function.

Could you imagine Office using slow-as-molasses WinForms? That would be
funny.

WinForms is sluggish in my experience -- controls generally flicker a lot
and are very slow to be painted on-screen initially. Every WinForms app
I've ever used is so laggy that I don't generally like using the app (even
if it's an otherwise decent app).
.

Relevant Pages

  • 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?
    ... How does "clickonce" solve the problem up version updates? ... takes longer to develop ASP.NET interface than a windowsform app ... > developer can choose how they want to communicate -- direct to SQL ... using winforms requires that the client has the .NET framework ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Are ASP.NET user interfaces essentially dead now?
    ... proper care and then there is jumping thru hoops, you want to avoid the hoop ... takes longer to develop ASP.NET interface than a windowsform app ... developer can choose how they want to communicate -- direct to SQL servers, ... I see Winforms doing the major amount of interface work and leaving the web ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Are ASP.NET user interfaces essentially dead now?
    ... clickonce solves it in terms of the user ... receiving the latest copy next time the app is run. ... using winforms requires that the client has the .NET framework ... >>> make a web service call back to the web server for example. ...
    (microsoft.public.dotnet.framework.aspnet)