Re: Mainstream Apps using DotNet


I think the answer to your question lies in what types of applications you
are writing. If you have to get down to really low level programming - then
you may want to stick with C++. However if you understand the paradigm of
managed code (i.e. with is nothing new - it's just the concept that you have
another layer running underneath you - which is the .NET Framework. Other
platforms like Java and Progress have run under this scenario for years) then
..NET wins hands down in so many areas that's it's not even funny (imo).

....they (MS) have just upped the game in so many ways in terms of
productivity etc. that you can't go wrong if you choose to adopt this
platform and stick with it.

(just opinions)

--
Franklin M. Gauer III
Applications Development Manager
Integrated Companies, Inc.


"Radek Cerny" wrote:

The re-engineering thing is one fear I absolutely do not have - all of my
precious logic is server-side. Only my GUI classes are deployed, and of
course the layout - simply placeholders. Everything else is safely behind a
WebService facade. To develop something similar in any other environment,
including Java, would have been far more difficult, if not impossible.
Looks, works and feels like a rich windows app, but is merely a facade. And
repeating, biggest issue is PC's NOT having the .Net framework installed.

Cheers,

Radek

"Robert Johnson" <johnson_r@xxxxxxxxxxxxx> wrote in message
news:%23IsrzHVoGHA.4404@xxxxxxxxxxxxxxxxxxxxxxx
I have been working in a 4GL environment for many years also. It seems to
me that the versatility offered by dot net is far surpassed by anything
offered by the more conventional programming environs.. I just don't see
any problem with going with the dot net route. Sure the dot net apps can be
reverse engineered but so can my win32 apps. Of course there is always the
down side, the "Cost of doing business" but if the benefits outweigh the
costs.. then it becomes a no brainer as far as I'm concerned.

my 2pennys worth...

Robert

"Radek Cerny" <radek.cerny@xxxxxxxxxxxxxxxxx> wrote in message
news:O35tJtUoGHA.4688@xxxxxxxxxxxxxxxxxxxxxxx
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: Honestly Curious
    ... On Windows, I agree, this is a PITA--but not so on other systems that don't implement OS X-style application containers. ... It also makes abstractions more difficult to implement, and introduces the potential to break scripts and applications that call on other applications. ... Since I use quicksilver as an application launcher, along with a very few "always used" apps on the dock, it makes no difference to user functionality where the apps reside, but it does help organize data together on the storage media. ... case though, there is nothing that should dictate that all applications land on the boot drive, unless the other drives are removable. ...
    (comp.sys.mac.advocacy)
  • Re: Newbie FAQ #2: Wheres the GUI?
    ... I think the exact opposite argument is better: because web apps are ... Desktop applications don't usually have a full text and graphics ... Either the data is remote, ... Might as well write a linux emulator on Windows ...
    (comp.lang.lisp)
  • 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: Proof of the Macs intuitiveness
    ... just as easily use the Mac's Application folder (though you can have ... applications in other areas, such as an Applications folder in your ... Adobe apps, for example, act like Windows ...
    (comp.sys.mac.advocacy)
  • Re: Confusion Apple installs...
    ... > Still don't get the way OSX handles files, applications, and directories. ... It's certainly not intuitive to refugees from the Windows or Linux ... Finder window pops up with ... and creating sub-folders to group similar apps ...
    (comp.sys.mac.advocacy)
Loading