Re: Winform vs Webform: how to choose?

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: alf (em_alf_at_hotmail.com)
Date: 10/27/04


Date: Wed, 27 Oct 2004 22:48:12 +0200

Only there are one adventage form webf. to winforms this is deploy.
Microsoft and other manufacture are crea thecnology to automatically deploy
like oneclick.
May be you use software in chached mode or simiare donwloading adn
installling /desinstalling automatica when you no use bat always when you
split you win and is a estupid idea use a powerfull pc only for rendering
html pages. is better spread along pc code al work millinon on processor and
no only one big processor in a webserver..

spanish man idea.

-_-

"Dean Slindee" <slindee@charter.net> escribió en el mensaje
news:10n34j686fcjdfa@corp.supernews.com...
>I would like to hear some practical comments about how to decide whether
>aly
> new application becomes a Winform vs a Webform application. Would you say
> that every app should be, by default, a Winform app unless it positively
> cannot be (for some technical reason). Or vice-versa?
> Obviously, Visual Studio could never be a Webform app because it requires
> a
> lot of CPU cycles.
> It appears to me that there is a broad sort of continuum in application
> characteristics. Some apps are natural Winform apps (VS Studio), while
> others are natural Webform apps (heavy textural content, non-updated).
> However, between these two poles, lies most of the rest of the today's
> apps.
> How do you decide which pole the new app should gravitate toward?
>
> Here is a quote from Alan Cooper, just to raise the temperature and get
> you
> started thinking (can you rebut this if you are a Webform afficionado):
> "The browser is a red herring; it's a dead end. The idea of having batched
> processing inside a very stupid pro­g­ram that's controlled remotely is a
> software architecture that was invented about 25 years ago by IBM, and was
> abandoned about 20 years ago because it's a bad architecture. We've gone
> tremendously retrograde by bringing in web browsers. We have stepped
> backward in terms of user interface, capability, and the breadth of our
> thinking about what we could do as a civilization. The browser is a very
> weak and stupid pro­g­ram because it was written as essentially a master's
> thesis inside a university and as an experiment."
>
> Thanks,
> Dean Slindee
>
>



Relevant Pages

  • Re: Starting exe from WebService
    ... Ok, when you said it was WinForm app that you were trying to execute, I ... > WebService because the program is complicated and I don't ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Relationship between Application.Exit() and AppDomain
    ... Yes, the app we are writing is being coded in Winform, it's not a Web ... trying to create an app that would host some other applications, either GUI ... AppDomain to host the 3rd party code for security/robustness reason? ...
    (microsoft.public.dotnet.framework.clr)
  • RE: 2.0 DataSources vs. TableAdapter/Datasets
    ... components in winform application and asp.net application, ... application is desktop app where all the class instances and componets live ... | There are articles on the new TableAdapters where it says that a key new ... | common datasources for the whole project (accessed via the Data menu ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Taskvisible and NotifyIcon. Not supported. Why?
    ... QB has to be able to launch the app automatically, ... > TaskVisible Property Changes in Visual Basic .NET ... the other is a WinForm application. ... > responsible for background data manipulation say, ...
    (microsoft.public.dotnet.general)
  • Re: auto mouse click
    ... like i said i'm using a winform to create this program. ... > wanted to create a windows app that would play a web-based slot machine game ... > app to play this web-based free slot machine game. ...
    (microsoft.public.dotnet.languages.vb)