Re: VB6 - VB.NET post SP6

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Dave McIntosh (dmcmail56-io_at_yahoo.co.uk)
Date: 04/19/04 

Date: Mon, 19 Apr 2004 12:09:07 +0000 (UTC)

Thanks for the pointers to Whidbey.

I am in the process of checking it out on MSDN and elsewhere.
The reintroduction of Edit & Continue is welcome. I just hope it is a full
reintroduction and does not have limitations that are being kept quiet for
now!

The next big issue with .NET for me is the Framework requirements that are
put on the "would be" end user. Frankly it's a mess and looks like it will
continue to be so for a while. (Users can have no Framework, V1.0, V1.1
...V.Whidbey?) If the small time application developer wants to target his
product at a general audience, then he/she has to have confidence that there
isn't going to be a big problem in deploying it.

With VB6 you have an overhead of only few MB's of run times; it seems to me
that the NET Framework is a model that will be in continual development and
that developers will be struggling with the desire (need?!) to use the
latest version and the worry that their users will (probably) have to
download 30MB or whatever of Framework.

Maybe Microsoft (still) just don't care about anyone other than the
"professional" corporate developer.

    Dave.

"Rob Windsor [MVP]" <rwindsor@NO.MORE.SPAM.bigfoot.com> wrote in message
news:%23ge3HDbJEHA.1944@TK2MSFTNGP10.phx.gbl...
> Dave,
>
> Visual Basic 2005 (a.k.a. Whidbey) will add quite a few RAD features that
> should help you out:
> - Greatly enhanced debugging features including Edit and Continue (what
you
> called edit-retry)
> - Simplified database access and binding
> - Simplified access to the most commonly used parts of the framework
through
> the "My" classes.
>
> While I don't think VB 2005 will achieve the "out of the box" experience
of
> VB Classic, these changes plus others will definitely reduce the learning
> curve for developers transitioning into .NET.
>
> --
> Rob Windsor [MVP-VB]
> G6 Consulting
> Toronto, Canada
>

Relevant Pages

  • Re: .NET Framework - how important?
    ... Framework, with the developer not knowing or assuming that the developer's solution was the only solution using the Framework. ... The runtime component of the .Net Framework is not a 3rd party component. ... It is a mistake by the developer to uninstall the runtime component of the Framework, with the developer not knowing or assuming that the developer's solution was the only solution using the Framework. ...
    (microsoft.public.windows.vista.general)
  • Re: [PHP] Zend Framework...where to start? -- dont.
    ... I've not used Zend myself, so I can't say for certain, but the above ... the most given they actually make PHP, but at this point in time, I would ... never choose to use a bloated framework. ... Will the new developer who is learning how to use ZF realize ...
    (php.general)
  • Re: .Net environment opinions
    ... Is .Net a shit environment or should I "shoot the developer" ... Microsoft Dev community) before it ever makes it out into the wide ... Sure - there might be the odd bug in the framework (just ...
    (uk.rec.motorcycles)
  • Re: Tired of 100s of stupid Getter/Setter methods
    ... >> generally acknowledged to be one of the few great failures of that API. ... > asked me to demonstrate a problem with the Collections framework. ... appropriate warning in the API docs for the data framework... ... doubt the developer read the documentation before doing so last time, ...
    (comp.lang.java.programmer)
  • Re: VB6 - VB.NET post SP6
    ... >The reintroduction of Edit & Continue is welcome. ... >The next big issue with .NET for me is the Framework requirements that are ... >that developers will be struggling with the desire to use the ... Let's face it Dave, Micro$haft doesn't care about anyone other than Micro$haft ...
    (microsoft.public.vb.general.discussion)