MVPs pass this along to Microsoft - Please

[Guest]

Sticking to VB6 because I am an Engineer that does not want to spend my time
trying to figure it all out, .NET that is.
I will wait, as I did for VB6 to come out (as a BASIC Professional
programmer), until VB.NET is mature enough and has the support needed.
Specifically libraries of code snippets that I can "steal" and rework for my
use.
I do not see that happening for another two years.
We are seeing .NET evolve as did VB1 thru VB6.
Until Microsoft changes Windows so I cannot use VB6, I will continue to use
VB6 - it does the job!

Thanks for the ear.

 

[Cor Ligthert [MVP]]

Lorin,

I don't know what you mean with pass this along to Microsoft, however for
VBNet, from which I assume that you are talking about, are endless websites
with code samples by instance inside the MSDN webpage however as well from
others as by instance ours.

http://www.windowsformsdatagridhelp.com/default.aspx

(In our Link page you find more, while that is probaby not even 1 procent of
it)

In the next version of VBNet is (november 2005) even special right click
parts to insert snippets standard in your code. (Probably because there is
so much is the biggest problem to manage that).

Therefore what has there to be passed?

Cor

 

[Nick Malik [Microsoft]]

Sticking to VB6 because I am an Engineer that does not want to spend my
time
trying to figure it all out, .NET that is.
I will wait, as I did for VB6 to come out (as a BASIC Professional
programmer), until VB.NET is mature enough and has the support needed.
Specifically libraries of code snippets that I can "steal" and rework for
my
use.
I do not see that happening for another two years.
We are seeing .NET evolve as did VB1 thru VB6.
Until Microsoft changes Windows so I cannot use VB6, I will continue to
use
VB6 - it does the job!

Thanks for the ear.

Hello Lorin,

First off: I am not a member of the Visual Studio product team, nor am I
associated with them in any way. I just want to get that out on the table.

That said, I find your post interesting. I'm aware that there are some VB6
developers who have preferred not to take up VB.Net. Of course, this is
perfectly fine, and your apps will continue to work as expected (although
they may look a little different under Vista).

It is good that you consider VB.Net to be "maturing" although I consider
this to be a curious statement. I have written software in every version of
VB (I even sold an app written in VB 1.0 for DOS... that was a LONG time
ago). VB matured at every step of the way. I am not alone to consider
VB.Net to be a clear and obvious next step from VB6, although MANY would
disagree with me. Certainly, when I was a VB4 programmer, most of the
suggestions I saw aimed at the VB team surrounded the notion of "add object
orientation." When VB.Net did just that, I found it perplexing that folks
felt that the language took a step backward.

That said, the newest version of VB.Net attempts to smooth that transition
by putting in (some would say "putting back in") some of the features that
were more inherent to VB6 than to C++. This includes things like the VB
debugging abilities and the my. object.

Now that there are SUBSTANTIAL libraries of code with snippets that you can
use (I would suggest that there is easily more code available in VB.Net than
in VB6 now), and the language has made steps to smooth the transition to
object oriented development, I hope that you can now begin to try the new
features of the VB language.

I think you may like what you find.

--- Nick Malik [Microsoft]