Re: How's dot.net doing nowadays?

Schmidt wrote:
"Robert Conley" <robertsconley@xxxxxxxxx> schrieb im Newsbeitrag
news:af3ad9f5-2a87-45d5-aa06-899540227dd1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Jan 18, 8:59 pm, "Schmidt" <s...@xxxxxxxxx> wrote:
"Robert Conley" <robertscon...@xxxxxxxxx> schrieb im
Newsbeitragnews:a673c90d-d02c-4bc0-a55e-fa67de2cb526@xxxxxxxxxxxxxxxxxxxxxxx
s.com...

Do you mean something like the <Ctrl><L>,
which is available for Debugging in VB-Classic?

No I mean when you get an error in .NET the err object
contains the stack trace.
Ok, nice to have - one point for .NET - but (in the
context of this discussion) - not a showstopper regarding
the functionality of a well written Classic-App.

So right out of the box you get functionality that you
have to pay money or spend time in VB6.
Read comments below.

And yes, in most cases an older App is based
on constructs (the selfwritten "framework" if you want),
that is not suitable (over time - when the App grows).
Then, if you get a chance to do a clean rewrite
of the App, you know better and don't make that
many "mistakes" - I think that is the effect Chris sees now,
but this is something you would see too, if you'd have used
VB-Classic for the rewrite - it is nothing related to the
"power of .NET".

Wrong, because because the more lines of codes it takes
to make a function work the more chances bugs will occur, ...
I thought, we discuss the issues of a grown VB-Classic project,
developed by experienced Classic-Developers over years.
In this context you already (should) have, what you typed
above: "tools you already spent money" and/or tools you
wrote yourself, to write less lines of code for the type of
application you are developing/maintaining.

It is the same old discussion about the "productivity-gains",
.NET has to offer - I think they are not as big, if you already
have "your additional tools at hand" in VB-Classic.

Think I will have to prove my claim with an appropriate (small)
Demo-App in the next months - then all the .NETers out
(t)here can try, to reach the same functionality with less
lines of code in .NET.
No offense, just wait until I come up with this.

Olaf


True, we have all the tools we need to keep maintaining out classic VB6 app. True, we don't *need* anything more. BUT... In terms of scalability and maintenance costs... it's no longer worth it. Our VB6 app is a dinosaur... it's time it picked up a club and started walking on two feet. It's over a decade old, and it looks it. Does it function? Sure, I suppose. But there's also room for improvement. There's things we'd like to do differently than what we did the first time around.

In our shop, there's mix of productivity AND user experience that drives our desire to move to .NET. We're not interested if it takes more lines or less lines, because the conversion (at least in our case) isn't a 1-for-1 conversion. Things will get moved around, split up, combined, what ever makes sense.

In theory, there's nothing that's forcing us to move to .NET other than our own internal desire to do so. There are things that .NET offer us that we can't do with VB6 (inheritance, #1). If we wanted, we could probably continue to build and maintain our app in VB6 for the next decade. Sure maintenance will be a nightmare, and there are pieces falling apart, but hey, we've got all the tools we need right here. Right?

Our plan consists of fixing all of the past mistakes, and make all new ones. After all, isn't that the dafynition of "Upgrade" - to take out old bug and put news ones in?

-ca
.

Relevant Pages

  • Re: Playing with the Dark Side
    ... functionality. ... Now if I could easily import my VB6 code, then that would be good as I could ... app, which is definitely something I don't do. ... It does do a lot of things well but it also has a hacky element to it. ...
    (microsoft.public.vb.general.discussion)
  • Re: Using VB6 dll in Delphi app.
    ... I have to ask why not write the whole thing in vb6 or delphi? ... app into another separate app which is written in ... functionality had to be duplicated and different parts of the app couldn't ...
    (microsoft.public.vb.general.discussion)
  • Re: N-Tier Design Question?
    ... but sharing the same class definition. ... > I understand exactly what you are saying, but when I spoke of Business ... >> organizes and maintains all functionality for a single user of your app. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Loading VB files?
    ... How 'bout finding something that'll get VB6 source from an app it ... does it take to start the first dotNet app of the day?... ... functionality", mmmkay? ... tells me these "knowledge or skills" are about 15 years behind... ...
    (microsoft.public.vb.general.discussion)
  • Re: Architectural feedback
    ... > bank branches absolutely must be able to function with a failed server (or ... This means a lot of functionality is duplicated on ... >> core app must reside on the client or may be run from the server. ...
    (microsoft.public.dotnet.general)