Re: Microsoft and Trust Take 2

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hey Michael,

Perhaps the reason you are not getting a straight answer is because the
question lacks support. Can you quote anyone explicitly telling a poster to
use VB6 and not .NET? Most likely, there is a valid reason for the
recommendation, whether it is advising to use VB6 or .NET.

I am sure you could find various quotes, but I have also seen people here
advise the posters to use .NET:

"If you have just started VB, then you should maybe think about using
..NET because you can apply skinning much easier in that."

J. Johnsen,
"Can anyone recommend free skinning s/w for VB6?" 2008-03-28 5:38AM

Recommendations go both ways, depending of the task at hand.

Basically, I can think of three answers to your question:

Why is VB6 recommended and .NET .not if they are both from MS?

1. Technical: The job at hand can be done more simply using VB6 as
opposed to a .NET language.
2. Cautious: MS left the developer hanging with VB6 code with no
migration road to the next generation once already. For better or
for worse, VB6 is now stable in this regard, so better go with
this technology than risk your code assets (again) with .NET
3. Visceral: I hate .NET, period.

While I would caution against making a decision based on #3, the
other two points are valid (IMHO); however, there will be the case
where the developer must weigh the pros and cons of each one and
possibly strike a balance between the two.

Saga
--



"Michael C" <mike@xxxxxxxxxx> wrote in message news:%231wb0y5kIHA.5396@xxxxxxxxxxxxxxxxxxxxxxx
I know I asked this question already and got some 300 replies or so but I think everyone did a
stellar job of avoiding answer the question. 300 replies and no answer must be some sort of record
:-) So here's the question again. What I don't understand is why recommend against using .net
because MS *might* cut you off when we don't recommend against using VB6 even though there is a
100% certainty of getting cut off.

"As many here have said, MS cannot be trusted with our development
environments. MS are dishonest and have little regard for the work we've put
in over the years. Therefore we should not use dot net. Yet many here still
recommend using VB6 even for new projects. If MS are so untrustworthy
shouldn't the same amount of effort be applied to warning everyone to avoid
VB6?"

Michael



.

Relevant Pages

  • Re: Can Dotnet and VB6 exist in harmony on the same pc?
    ... > Yes, it's a good idea to compile to the lcd, however, I believe the xp ... > totally unique by itself and should be addressed separately regardless. ... distribute vb6 ...
    (microsoft.public.vb.general.discussion)
  • RE: COM interop
    ... Commonly we did not recommend you do that. ... Because VB6 Form and .NET forms ... Microsoft Online Community Support ...
    (microsoft.public.dotnet.framework.interop)
  • Re: Microsoft and Trust Take 2
    ... 300 replies and no answer must be some sort of record :-) So here's the ... when we don't recommend against using VB6 even though there is a 100% certainty of getting cut off. ... Therefore we should not use dot net. ...
    (microsoft.public.vb.general.discussion)
  • Re: 12 year old programmer to be
    ... I recommend using your copy of VB6 to teach him the basics of programming. ... C++ or the .net languages so I would use VB6 to begin with. ...
    (microsoft.public.vb.general.discussion)
  • Re: C.NET VS VB6
    ... AK i would recommend that you start reading an introductory chapter about ... Well it is all a mather of preferences as a experienced VB6 and VB.Net ... far as scope creep to add features, and I am trying to look down the road. ... target features closely match their capabilities. ...
    (microsoft.public.dotnet.languages.vb)