Re: Back to VB6 and .NET

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

You also failed to mentioned that desktop application development is
down considerably. Web
application development opens up quite a few different options for
developers.

I'm moderately convinced that that's a fad. I know in our shop, we tried
moving some stuff to Intranet, and while some of it is quite nice there
and
very convenient since we don't have to roll out desktop apps, my boss
quickly realized that not EVERYTHING belonged there, and that the Desktop
version was far more functional under the clunky old Access 2000-2003 than
the web version of the the app was.?



Often "cutting edge" can be "bleeding edge".

I'm originally from Pennsylvania, but relocated. Last time I was in PA
visiting family, I talked with a friend of mine that's in management at a
company I did a little work for years ago ("little"... actually it was quite
a large and encompassing account management system, done primarily in VB6).
Anyhoo, he tells me that they wanted to add a couple of features to it,
features that could have easily been done with VB6. But they brought in
some guy that re-engineered the whole damn thing in dotnet and "converted" a
couple of things to web services (which wasn't necessary or even beneficial,
just the "in thing" I guess). They paid the guy a ton of money for the year
+ project. My friend tells me that the damn thing is as slow as molasses
and they get daily complaints from the sales and CS personnel because it's
so damn slow and awkward to use... takes too long to pull up invoices, etc.
Even though the guy kept the same user interface layouts, user flow, etc.,
they weren't happy. All for the sake of being "in style", because one of
the VP's wanted "cutting edge". When he told me of the new things they
wanted added and I said it wouldn't have been a big deal to incorporate
those desired features into the "old" system (using VB6), he just shook his
head. I chuckled a bit.


.

Relevant Pages

  • Re: VB6 vs VB .Net
    ... If you decide to stick with VB6 for a while longer, ... even more so than any other .NET language. ... but also due to the improved language features. ... On the client side of things, especially as it sounds like you will be doing ...
    (microsoft.public.vb.general.discussion)
  • Re: Newbie Advice/Critiscism
    ... the Office Development Team and the Language group. ... There were papers and some 'demos' showing these features. ... started phasing out VB when VB6 was released. ... didn't mind that much, as it was after all, Beta 0.9. ...
    (microsoft.public.vb.general.discussion)
  • Re: edit and continue
    ... > Yeah, but sometimes I'll align a bunch of controls on their left edges, ... There's literally hundreds of small features that are all a little bit ... making .net highly compatible with vb6 would have hobbled it in some ways. ... Generally the IDE just disappears checking in or out a ...
    (microsoft.public.vb.general.discussion)
  • Re: C.NET VS VB6
    ... development environment just as C# and J# C++.Net etc etc ... Well it is all a mather of preferences as a experienced VB6 and VB.Net ... Our proposed app's target features consist of a business ... target features closely match their capabilities. ...
    (microsoft.public.dotnet.languages.vb)