Re: How's dot.net doing nowadays?

mayayana wrote:
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.

Finally, a .NetHead has presented a cogent case
for moving to .Net: It's the height of fashion.
By all means, sign me up!


First I resent the term .NetHead ... .NET for our app makes sense because the time is right. If I were a .NetHEad, then I would have bailed years ago to work for a full .NET shop. VB6 is alive and well. And for some cases, still serves its purpose very well. There are things that VB6 will forever be better suited for than a .NET app. But we have outgrown the abilities of VB6. It's called progress.... it's attitudes like yours and some of the others I've seen out there (here, and other places), that would still have us working in 16 colors using command line applications written in BASIC for DOS1.2.

The users expect more. Our app doesn't scale well. And we know that. The birth of .NET is the first chance we have to correct that problem. It's also giving us the opportunity to tighten security and auditing. Our clients fall under the scope of Sarbanes/Oxley and as a result, some of them have had to scale things back because parts are not in compliant.

There will be the nay-sayers. I accept that. There will be the proponents. I accept that too. If you hate .NET so much, don't friggin use it. It's just another tool in a developer's arsenal of weapons. Use the right tool for the right reason.

Next, why is it that 8 of 10 .Notters will quote something out of context so they can twist its meaning? If you quote someone, and argue it, have the decency to quote the whole thing and then argue it.

If some one is moving to .NET, or if the reason some one changing ANY platform is simply because it's the fashionable thing to do for the week, then it's a bad decision. Make the change for the right reason. That's what we're doing. It's time to give our app a face lift. Inside and out. It's not like we're just doing this will-nilly, we've been slowly moving in this direction for a little over three years.

-ca
.

Relevant Pages

  • Re: Hows dot.net doing nowadays?
    ... VB6 is alive and well. ... Our app doesn't scale well. ... If some one is moving to .NET, or if the reason some one changing ANY ...
    (microsoft.public.vb.general.discussion)
  • Re: MS, Enough is Enough!
    ... There's no reason it shouldn't be possible to import a VB6 ... app into .net and have it run pretty much straight off. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB calling DLL only with _stdcall?
    ... I'm a fan of dot net but I don't think there is any reason to use it in ... this case if your app is all in vb6. ... Well, I'm a hobbiest programmer but this app is relativily popular, so I'd ...
    (microsoft.public.dotnet.languages.vb)
  • Re: VB calling DLL only with _stdcall?
    ... I'm a fan of dot net but I don't think there is any reason to use it in ... this case if your app is all in vb6. ... Well, I'm a hobbiest programmer but this app is relativily popular, so I'd ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Opinion wanted
    ... the details including the nature of my own app (which you mischaraterized ... correct the current control (provided that control is invalid but invalid ... causes you to validate controls that have already been ... largely discreditted for good reason and has very little use these days. ...
    (microsoft.public.dotnet.framework.windowsforms)