Printable View
Now that everybody is talking about this new development package and the beta has arrived, how many of you are going to go right ahead and purchase it once it is released? Or does it just need time to mature and get rid of its slowness/bugs?
Things to consider:
1. Is it a good thing that all the languages
use the same program?
2. Will it actually make life easier?
3. What do you think of the other new additions
to the syntax?
chilibean
1. Is it a good thing that all the languages use the same program?
Depends on how many languages you know, and the app you're working on. For me - no as it slows the bloody system down too much
2. Will it actually make life easier?
Yes
3. What do you think of the other new additions
to the syntax?
Some good, though the amount of extra crap thats in the form was a little confusing at first.
overall, I'll buy it as I love it so far, but I'll get a Gazillion Mhz, 8billion MB Ram PC first so I can actually run the thing like vb6 now.
Anyway, this should be in the .net forum. The chit chat one's for taking the p!ss out of other forum members like Katie ...;)
I like the sound of a lot of the new features but I can say that I won't consider upgrading to .NET until it supports control arraysl.
control arrays will be obsolete, i'm not sure what changes theyre going to do yet about the current eventhandling system based on the delegate model, but forget about control arrays.
i have VB5 and i am happy with it. I do not plan to buy VB.NET because, the original Visualbasic Language (developed by an university in the US) will not be VisualBasic anymore. microsoft decided (again) go change it to their version like they did with HTML and Java (sun microsystems)... They change the code of it so, you will have to use internet Explorer to view certain web page...
In my opinion, i'll stay with VB6...
I suspecyt ,that as with all other times VB has changed, we will need to be proficient in a number of different versions. At one stage when VB 6.0 came out, I had just finished doing a VB 5.0 job and my next job was taking 16-bit VB 4.0 code and converting it to VB 6.0.
There will be plenty of VB 6.0 work for the next couple of years, but if we are to make a living at this we will have to evolve to VB.Net or go the way of the dinosaurs (yes, I am talking about COBOL programmers ;)).
Just my couple of pennies worth,
SD
If control arrays become obsolete due to structural changes in the language, then fair enough; I would be interested to know the nature of the changes that make them obsolete. What is the 'delegate' model?Quote:
control arrays will be obsolete, i'm not sure what changes theyre going to do yet about the current eventhandling system based on the delegate model, but forget about control arrays.
:confused:
It's all about Event wiring, delegates that attaches eventhandlers with controls, i haven't seen any samples so i can't say how the implementations are going to be, but M$ says there's enough RAD tools for hiding the event wiring itself, here's a sample in c# though
http://msdn.microsoft.com/library/do...ini-sample.htm
here's some more info on the event concept:
http://msdn.microsoft.com/library/do...tsoverview.htm
Does Micro$oft's VB.NET support the MouseOver Function for objects yet...? :(
I have no idea, but i made an activeX dll, you can use for any control that has a handle, let me know if you need it
I was practicing sample apps with .NET, but left it for a while.
A recent post has made me realise I need to keep practicing with it as I don't know it well enough yet.
Any ideas for small apps I could write on it please ?