Re: Mainstream Apps using DotNet

I came from a 4GL background, have spent some time in other native win32
environments, and I must say that .NET is definitely the way to go. Unless
you have some extreme gdi requirements (I wouldnt write a video renderer in
..Net). Only drawback is that not every PC has the framework installed. MS
decided to pull it from SP2, and this has frustrated me no end.

Good luck.

"Jim" <nospam@xxxxxxxxxxxxxx> wrote in message
news:PS5rg.275695$8W1.233082@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks for your note.

Unfortunately the type of applications I develop aren't suited to running
over the internet yet. As the users will most probably not have access. I
appreciate that for web application development, then .net is one way to
go, ...and something to consider if I think that there is any chance I can
make my users go that route.

But to clarrify from the original question, I was trying to guage where
the current momentum is with regard to writing software to run locally
under Windows, on a rich client. As with traditional Windows Application
software. e.g. are win32 tools, such as VC++6, Delphi etc still prefered?
over .net for traditional Windows Applications.

Many thanks

Jim

"Radek Cerny" <radek.cerny@xxxxxxxxxxxxxxxxx> wrote in message
news:%235c68XNoGHA.4332@xxxxxxxxxxxxxxxxxxxxxxx
Jim,

whats in a name? DotNet. Kinda implies a web-centric development
environment. We've got live clients on a hosted ERP/CRM/Financial
system, deployed purely as WebServices. All DotNet. Accessible via Rich
Clients (DotNet + anything that consumes WebServices), PDA's (yep -
DotNet Compact Framework), AJAX etc.

Your question was leading down a funny path. Our apps are Windows apps -
they look, feel and work like typical Windows Apps, but all the "logic"
and persistence resides on a WebServer somwehere in the ether.

None of this is really achievable without WebServices and DotNet in
general.

Cheers,

Radek

"Jim" <nospam@xxxxxxxxxxxxxx> wrote in message
news:yFOqg.273746$8W1.56397@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Cor,

Whilst trying to track down some answers to this question, I've seen the
question asked also, but not really found anything conclusive.

I suppose the underlying intention of the question is to see how well
.net is actually being adopted as "the" Windows Application development
enviroment, or if software houses are keeping with traditional Win32
tools.

I see lots of books and websites etc all devoted to.net, but as far as
mainstream applications go, I'm not aware of any that use .net. I'm
trying to try and work out who is using the framework for WinForms, and
to determine if the trend is for more and more .net applications, or
whether Win32 is still the more dominant Windows Application
environment. - Which is something that will help me to decide if it's
worth basing my next applications on .net or win32.

My thoughts were that if some of the bigger software houses were now
using .net, then the trend would seem to be leaning towards .net. But as
yet, I'm not sure.

Many thanks

Jim

"Cor Ligthert [MVP]" <notmyfirstname@xxxxxxxxx> wrote in message
news:OEjo6jCoGHA.1300@xxxxxxxxxxxxxxxxxxxxxxx
Jim,,

This is very much asked and answered in this newsgroup, but can you
give us the main intention of this question. Often it leads to long
trolling threads.

Cor

"Jim" <nospam@xxxxxxxxxxxxxx> schreef in bericht
news:GFLqg.273648$8W1.232110@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
With .net having been around for a while now, does anyone know what
the uptake of major software houses is in using .net for Windows
Application development? e.g. have the likes of Adobe, MS, Corel, etc
actually released any applications that use the framework?

Jim











.

Relevant Pages

  • Re: Managed vs Unmanaged Bare Bones Performance Test
    ... One of the reasons that things like Virtual PC (which runs Windows on pre-Intel Macintoshes) and Rosetta work so well is that the programs being run spend very little time in the code that needs to be translated. ... If your code only spends 1% or less of its time executing the code you actually wrote, and the rest of its time either waiting on i/o or executing libraries in the operating system, then even if you have a 20X difference in performance, you're only really looking at a 20% cost in the "slower" environment. ... There are a few classes of applications where this sort of difference matters. ... The biggest thing I notice in my applications is start-up time, as the .NET Framework imposes a relatively large burden with respect to application initialization as compared to a straight Windows application. ...
    (microsoft.public.dotnet.framework)
  • Re: Mainstream Apps using DotNet
    ... I have been working in a 4GL environment for many years also. ... reverse engineered but so can my win32 apps. ... Unfortunately the type of applications I develop aren't suited to running ... As with traditional Windows Application ...
    (microsoft.public.dotnet.general)
  • Re: Mainstream Apps using DotNet
    ... To develop something similar in any other environment, ... Looks, works and feels like a rich windows app, but is merely a facade. ... reverse engineered but so can my win32 apps. ... Unfortunately the type of applications I develop aren't suited to ...
    (microsoft.public.dotnet.general)
  • Re: Mainstream Apps using DotNet
    ... that Win32 has an edless life. ... mainstream applications go, I'm not aware of any that use .net. ... Win32 is still the more dominant Windows Application environment. ... My thoughts were that if some of the bigger software houses were now using ...
    (microsoft.public.dotnet.general)
  • Re: Mainstream Apps using DotNet
    ... I think the answer to your question lies in what types of applications you ... To develop something similar in any other environment, ... Looks, works and feels like a rich windows app, but is merely a facade. ... reverse engineered but so can my win32 apps. ...
    (microsoft.public.dotnet.general)
Loading