Re: Conversion Problem
- From: Tom Shelton <tom_shelton@xxxxxxxxxxxxxxxxxx>
- Date: Fri, 11 Jul 2008 11:23:36 -0500
On 2008-07-11, Ken Halter <Ken_Halter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
"Tom Shelton" <tom_shelton@xxxxxxxxxxxxxxxxxx> wrote in message
news:3rmdnZmPI7VnFOvVnZ2dnUVZ_qXinZ2d@xxxxxxxxxxxxxx
On 2008-07-10, John <no-email-supplied@xxxxxxxxxxx> wrote:
LOL... The problem is John, that you are not familiar enough with the
framework and .NET. Once you become so, on the whole things are MUCH
easier
...and he's not familiar with the framework because the help system sucks
like a hoover.
Please! And VB6's doesn't? MS help has sucked for years - fortunately,
there's this thing called the Internet....
then VB6. I know, I spent years doing VB work. I'm not claiming every
thing
is easier, just most.
Your example of control arrays is pretty funny - I
don't even miss them. First off, the main reason in VB.CLASSIC for
control
arrays was 1) common event handling and 2) avoiding the 256 unique control
names per form limit (or was it 255?). 2 doesn't apply in VB.NET and 1 is
256... and we can see "2 doesn't apply" from the over-bloated, "feature
rich" (aka bug fest) apps people create with dotNet.
As opposed to the "feature rich (aka bug fest)" apps in VB6? You know, VB in
general has a bad rep for a reason. It has more to do with the quality of the
coder, then tool.
handled by the fact that VB.NET events allow an event to be assigned to
multiple controls (heck, they don't even have to be the same type)...
...and, you're saying that's not possible in VB5/6? If so, you may not be as
"great" as you assume.
Duh, I said that was one of the reasons for control arrays? In VB.NET, they
don't have to be a control array and they don't have to be the same type. Or
are you claiming that you can have the same event procedure handle the
TextChanged event of a combobox and a textbox in VB6?
Public Class MyForm
Inherits System.Windows.Forms.Form
Private buttons() As Button = new Button() {Button1, Button2, Button3}
Too bad that's not VB syntax. It's B#... I've been using basic and assembler
since 1981 and basic has *never* used curly braces.
VB never had array or variable initialization on the same line before
either... A feature was added, and a syntax was chosen. Get over it.
That's "C".... plus,
when the app is done, the code is readable in basic (and assembler)... not
that framework/linq/xml crap.... guess what... linq or any variant of SQL is
*NOT* part of any basic language that makes sense.
You don't like LINQ - don't use it.
That's SQL syntax and
should stay as such. No use adding hundreds of keywords to an already
over-bloated environment
Your oppinion.
..
Private Sub DoCoolStuff(ByVal btnIndex As Integer)
Dim theButton As Button = buttons(btnIndex)
Very readable.... NOT
What? As opposed to:
Dim theButton As Button
theButton = buttons(btnIndex)
Sorry, but I think I like the one line rather then two bit.
As for your file issue, I only was half joking about your file access -
the
fact is that .NET is a different target platform then VB6. VB6 targeted
COM
...so, it worked.
Didn't say or imply that it didn't.
Which version(s) of the framework do your users need to
download?
Which ever version my app needs. That's sort of a stupid question - how many
Visual Basic runtimes are there? Oh, yeah one for every version.... And,
well were at it lets have a discussion about binary compatability, and dll
hell.
Microsoft surely doesn't make things easier on the developer. That
went away when VS6 did... and, if the whole mess is so freaking "wonderful",
why do they have to give it away free? You can still buy legit copies of
VS6, but be prepared to pay more than VS2008 costs... but, if you want what
you pay for, grab VS6
They give it away for very good reasons. VS's current competition is almost
all FREE. It's a market difference, and not a reflection on the quality of
the product.
Even after... what... 7? 8 Years? No one knows what to call this "B#"... is
it VB.Net? is it VB#? How about B#? or maybe it's VB8? VB9? What ever. Have
fun.
and so it has a lot of COM'isms - such as SafeArrays - and so in some ways
is
not compatable. Personally, if I were you I would create a VB6 component
that
would be able to convert the files into a more .NET friendly format and
then
Yeah... or maybe just write the thing in VB6 and go on to the next job, eh?
LOL... Yeah right. VB6 was a great tool in it's day, but compared to .NET
it's a toy. To do anything of more then average complexity requires jumping
through some major hoops, which often if not done properly lead to crashes and
hard to find instabilities. I can't tell you how often I read posts over in
the classic group that have long complicated answers delving deep in to the
API, that are solved in .NET apps in a couple of lines of code. But, if you
like dealing in complexity (aka bug riddled apps) then by all means, keep
clinging to your out of date toy environment...
But, like I said... you guys can have these freaking groups.
Thank you, your too kind.
--
Tom Shelton
.
- Follow-Ups:
- Re: Conversion Problem
- From: Ken Halter
- Re: Conversion Problem
- References:
- Conversion Problem
- From: John
- Re: Conversion Problem
- From: Patrice
- Re: Conversion Problem
- From: John
- Re: Conversion Problem
- From: Ken Halter
- Re: Conversion Problem
- From: John
- Re: Conversion Problem
- From: Tom Shelton
- Re: Conversion Problem
- From: Ken Halter
- Conversion Problem
- Prev by Date: Re: Conversion Problem
- Next by Date: Re: Conversion Problem
- Previous by thread: Re: Conversion Problem
- Next by thread: Re: Conversion Problem
- Index(es):
Relevant Pages
|
