Hard to use but a nice set of features, this .NET stuff is...

[Just_a_fan]

I have been really working to move up to VB9. There are some really
irritating parts of the interface that cost a lot of time across a day,
week, lifetime. But there is a lot to like, too. It has been real fun
learning the new stuff. Being sick gave me some extra time.

At first I thought I might never move off of VB6. I thought I would die
before it did and.. why move up, anyway. Well, I got MSDN and there was
this shiny new DVD (oh, yeah, IT DOES NOT INSTALL!!! YOU HAVE TO
DOWNLOAD FROM THE M$ SITE!)

So I loaded up the DVD, found it would not work, and not just for me,
then downloaded the .ISO, found a program to work with that, finally got
it installed and, only a few days later, was ready to start up the
ladder. (Aren't computers supposed to SAVE us time??? ...and make a
paperless office???)

I am only a rung or two up right now but I can see a great light coming
from a large opening at the top of the ladder. I may never get there
because .NET is just too big for most mortals to ever get all around but
striving is the thing.

Still wish they would at least sort the routines. What a waste of time
looking up and down to find the routine I want. And then scrolling
right out of it by accident, backing up, and finally doing what I want.
Terrible waste of an interface. But, as I always say: Windows and
almost everything else from M$ is written by High School kids. And find
frequently not finding phrases which are typed correctly and in the
project but cannot be found. (Aren't computers suppo... oh, never mind)

I know that computer school graduates would NEVER make error messages
like the following and keep them in the product FOR OVER A DECADE:

The file is in use. (Followed by equally inane "OK" and "Cancel")

or

The IRQ is in use.

and there are other wonderful examples but it is supper time.

I keep hoping that the giant will fully awake and provide good solutions
to basic problems like TELLING US ***WHAT**** file is in use!!! But I
grow hungrier and must quit thinking. My brain hurts!

Mike

 

[Cor Ligthert[MVP]]

Hi Mike,

Did you write this as well when you was going from Dos to Windows 3.11.

It has not much to do with VB for Net, more with the general change of
Window software.

Cor

 

[Harry]

I have been really working to move up to VB9. There are some really
irritating parts of the interface that cost a lot of time across a day,
week, lifetime. But there is a lot to like, too. It has been real fun
learning the new stuff. Being sick gave me some extra time.

At first I thought I might never move off of VB6. I thought I would die
before it did and.. why move up, anyway. Well, I got MSDN and there was
this shiny new DVD (oh, yeah, IT DOES NOT INSTALL!!! YOU HAVE TO
DOWNLOAD FROM THE M$ SITE!)

So I loaded up the DVD, found it would not work, and not just for me,
then downloaded the .ISO, found a program to work with that, finally got
it installed and, only a few days later, was ready to start up the
ladder. (Aren't computers supposed to SAVE us time??? ...and make a
paperless office???)

I am only a rung or two up right now but I can see a great light coming
from a large opening at the top of the ladder. I may never get there
because .NET is just too big for most mortals to ever get all around but
striving is the thing.

Still wish they would at least sort the routines. What a waste of time
looking up and down to find the routine I want. And then scrolling
right out of it by accident, backing up, and finally doing what I want.

There are two drop downs at the top of your code page. Start by having a
look at them. The right hand one displays all of your methods in
alphabetical order. This also list properties so you need to coordinate with
the left hand combo.

Terrible waste of an interface. But, as I always say: Windows and
almost everything else from M$ is written by High School kids. And find
frequently not finding phrases which are typed correctly and in the
project but cannot be found. (Aren't computers suppo... oh, never mind)

I know that computer school graduates would NEVER make error messages
like the following and keep them in the product FOR OVER A DECADE:

The file is in use. (Followed by equally inane "OK" and "Cancel")

You need to have a play around with the debug options to break on all
errors. Do a bit of investigating.

or

The IRQ is in use.

and there are other wonderful examples but it is supper time.

I keep hoping that the giant will fully awake and provide good solutions
to basic problems like TELLING US ***WHAT**** file is in use!!! But I
grow hungrier and must quit thinking. My brain hurts!

Mike

I used to be a dyed in the wool VB6 programmer, and also took up VB.Net with
considerable reluctance. I now find VB.Net (particularly VB2008) so
massively superior to VB6 that I dread having to do any code maintenence in
VB6 anymore.

The initial learning curve is very steep, however, the effort is well worth
it. There are many features not turned on by default. Have a look at things
like task list (you just put a TODO) anywhere in your code and it keeps
theep organised for you. You have the same for bookmarks.

The error list tab is brilliant. It records actually where error are and
with a simple click, takes you to that point, without running the project.

Have you had a close look at Tools/Options. You can setup the keyboard to
behave just like it did in VB6. The list goes on and on.

The biggest thing about .Net is objects, objects, objects. Learn to use
objects for everything, because .Net loves them. The combo and list box do
not behave like they did in VB6, instead they best use objects (you can add
single entries to the items collection). So, for a customer object, you set
a collection of customers as the datasource, set the displaymember to
CustomerName and the ValueMember to CustomerID. You can then use the
SelectedValue (CustomerID) or the SelectedItem to examine any property of
the object....the list goes on and on.

Stick to it buddy, VB.Net has a huge number of very pleasant surprises in
store for you, just be patient. It is a bit like the question of "How do you
eat an elephant?". The answer is simple; one bite at a time.

Trust I have not been to condescending.