Just happened to be scanning the web for something on VB6 and came across this monstrosity
in [Visual Basic]
|
From: MM on 30 Jan 2010 14:37 On Sat, 30 Jan 2010 10:56:03 -0500, "Nobody" <nobody(a)nobody.com> wrote: >"MM" <kylix_is(a)yahoo.co.uk> wrote in message >news:r928m5hcddusgimupbaej674ot9jt230qb(a)4ax.com... >> System.Globalization.CultureInfo.CurrentCulture.NumberFormat > >What does this have to do with VB6? Er, I was searching for stuff about VB6, as I think you'll be able to tell from the topic title. MM
From: Nobody on 30 Jan 2010 15:24 "MM" <kylix_is(a)yahoo.co.uk> wrote in message news:hh29m51qlokvdu1qvm5k5hbbpt16ba1k67(a)4ax.com... > On Sat, 30 Jan 2010 10:56:03 -0500, "Nobody" <nobody(a)nobody.com> > wrote: > >>"MM" <kylix_is(a)yahoo.co.uk> wrote in message >>news:r928m5hcddusgimupbaej674ot9jt230qb(a)4ax.com... >>> System.Globalization.CultureInfo.CurrentCulture.NumberFormat >> >>What does this have to do with VB6? > > Er, I was searching for stuff about VB6, as I think you'll be able to > tell from the topic title. But your post is about .Nxt, not VB6.
From: MikeD on 30 Jan 2010 16:45 "Nobody" <nobody(a)nobody.com> wrote in message news:##XtOpeoKHA.1556(a)TK2MSFTNGP05.phx.gbl... > "MM" <kylix_is(a)yahoo.co.uk> wrote in message > news:hh29m51qlokvdu1qvm5k5hbbpt16ba1k67(a)4ax.com... >> On Sat, 30 Jan 2010 10:56:03 -0500, "Nobody" <nobody(a)nobody.com> >> wrote: >> >>>"MM" <kylix_is(a)yahoo.co.uk> wrote in message >>>news:r928m5hcddusgimupbaej674ot9jt230qb(a)4ax.com... >>>> System.Globalization.CultureInfo.CurrentCulture.NumberFormat >>> >>>What does this have to do with VB6? >> >> Er, I was searching for stuff about VB6, as I think you'll be able to >> tell from the topic title. > > But your post is about .Nxt, not VB6. He was trying to make a point...that in .NET, you have to resort to digging into many layers to get what you want....whereas in VB6, what you need is usually right there. I get the point, but I don't see the purpose of making such a post in this newsgroup except to start more controversy. -- Mike
From: Nobody on 30 Jan 2010 17:38 "MikeD" <nobody(a)nowhere.edu> wrote in message news:O4DMcWfoKHA.1556(a)TK2MSFTNGP05.phx.gbl... > He was trying to make a point...that in .NET, you have to resort to > digging into many layers to get what you want....whereas in VB6, what you > need is usually right there. That's what Imports statement is for. It opens up a dotted branch, so you don't have to use the long dotted name. Kind of like not requiring that you type "Form1.BackColor", and just type "BackColor".
From: CY on 30 Jan 2010 18:50
On 30 Jan, 23:38, "Nobody" <nob...(a)nobody.com> wrote: > "MikeD" <nob...(a)nowhere.edu> wrote in message > > news:O4DMcWfoKHA.1556(a)TK2MSFTNGP05.phx.gbl... > > > He was trying to make a point...that in .NET, you have to resort to > > digging into many layers to get what you want....whereas in VB6, what you > > need is usually right there. > > That's what Imports statement is for. It opens up a dotted branch, so you > don't have to use the long dotted name. Kind of like not requiring that you > type "Form1.BackColor", and just type "BackColor". Might be that I think it was a bit of a stretch to post the original, but now an interesting thought does text1.text="something" and this might work but I wont use it text1="something" do? I used some java and the import or whatever it was called made me drop some of those long ones... I dont like the variant either, because you dont have to think on what you are doing, and if you do and still dont (happens) I get the results of pushing over 32767 registrable something (in VB int terms) and have to rewrite the stored proc or cleaning off data in the database.. isnt me.something to go with then? And for the .net yes seen it, dont like it... yet. (well U never know) //CY |