Just happened to be scanning the web for something on VB6 and came across this monstrosity
in [Visual Basic]
|
From: Ralph on 30 Jan 2010 21:07 CY wrote: > On 30 Jan, 23:38, "Nobody" <nob...(a)nobody.com> wrote: >> "MikeD" <nob...(a)nowhere.edu> wrote in message >> >> 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? > It would be a bit of a stretch. The Imports statement in .Net refers to Namespaces (usually libraries, classes, or both) within a context defined by scope. VB doesn't support Namespaces as all References and Modules are public (in project scope) by default, thus implicit. It does however support the ability to remove ambiguity by explicitly providing the reference or module of interest. The examples both of you used are dealing with 'object' references. Both ..Net and VB provide the With Statement to shorten the amount of typing needed when working with objects. -ralph
From: MM on 31 Jan 2010 03:56 On Sat, 30 Jan 2010 17:38:26 -0500, "Nobody" <nobody(a)nobody.com> wrote: >"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". You must be a .Net nut to want to take this thread further... MM
From: MM on 31 Jan 2010 04:40 On Sat, 30 Jan 2010 07:04:54 -0800, Tom Shelton <tom_shelton(a)comcastXXXXXXX.net> wrote: >On 2010-01-30, MM <kylix_is(a)yahoo.co.uk> wrote: >> I was looking for a masked textbox for hex input and in the MSDN blurb >> on How to Create a Numeric Text Box (.Net, naturally, this being >> Microsoft) my eyes hit upon the following: >> >> Dim numberFormatInfo As NumberFormatInfo = >> System.Globalization.CultureInfo.CurrentCulture.NumberFormat >> >> I mean, you REALLY have to allow that to sink in... >> System.... >> ....Globalization.... >> ....CultureInfo.... >> >> ....CurrentCulture.... >> >> ....NumberFormat >> >> Yeuch! >> >> MM > >I'm not sure your fellow VB6'ers should be very happy with you on this. You >mentioned .NET and now you have INVITED replies. Or, is it now ok to have >these discussions here? "INVITED" ? Where? MM
From: MM on 31 Jan 2010 04:42 On Sat, 30 Jan 2010 15:24:43 -0500, "Nobody" <nobody(a)nobody.com> wrote: >"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. It's about both, except I spell it .Net. MM
From: Nobody on 31 Jan 2010 05:23
"MM" <kylix_is(a)yahoo.co.uk> wrote in message news:jcham5lj914led9b0bk80su77rgbq2f0ci(a)4ax.com... > On Sat, 30 Jan 2010 17:38:26 -0500, "Nobody" <nobody(a)nobody.com> > wrote: > >>"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". > > You must be a .Net nut to want to take this thread further... Further from where? |