Heh. It is *not* Visual Basic. It is Visual Basic.NET. I fell into the trap of treating it like VB because the two languages share a common syntax.
I had originally switched to C# just to avoid this problem. To not fall into the mental trap of expected behavior from a faux familiarity. But I truly like the Basic syntax, so I've mostly switched back (or really, I just do both--but I preffer VB.NET). I wouldn't have made the mistake in C#. I just need to remember VB.NET is not VB. VB.NET is not VB. VB.NET is not VB. Like a friggin mantra. Stop saying things are broken, and realize that is just the way they are. Heh, as for people who are beginners in VB.NET with no VB6 experience... good for them. They will probably have a far easier time of it. Patrick Burrows Police at the station And they don't look friendly -------------------- Now Playing: mighty mighty bosstones - track 12 - -------------------- > -----Original Message----- > From: Mark Burns [mailto:[EMAIL PROTECTED]] > Sent: Monday, May 27, 2002 10:37 PM > To: [EMAIL PROTECTED] > Subject: Re: VB.NET Oddity > > > Patrick, > > Uhm...You are one of the more expert/experianced VB > developers out there, > right? > > ...and even you would "never have thought of that" in regards > to something > seemingly simple and relatively inocuous in this new VB.Net?... > > Tell me, does this tell you _anything at all_ about this new > "Visual Basic"? > (remember that the first word in Basic is supposed to be > "Beginners'"?) How > in the heck is a real, actual BEGINNER supposed to cope with > nuances like > these if someone like you gets hung up by these sorts of > "little things"? > > ...Just curious if you had any thoughts on this subject at > this point given > your experience using VB.Net... > > - Mark Burns > <former .NOTer - said for honesty's sake, not as a procliamation of > anything - I've backed off and attempted to remain neutral in > the .Net/.Not > religious wars in recent months> > > ----- Original Message ----- > From: "Patrick Burrows" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Sunday, May 26, 2002 10:02 PM > Subject: Re: VB.NET Oddity > > > > ---------------------- Information from the mail > header ----------------------- > > Sender: dotnet discussion <[EMAIL PROTECTED]> > > Poster: Patrick Burrows <[EMAIL PROTECTED]> > > Subject: Re: VB.NET Oddity > > > -------------------------------------------------------------- > ------------ > ----- > > > > Thanks, Mike, that worked. > > > > FWIW, I would never have thought of that. While I'm > formatting them as > > dates, at all time they are used and displayed as strings. > > > > Anyway, thanks. > > > > > > On Mon, 27 May 2002 11:57:31 +1000, Michael Weinhardt > > <[EMAIL PROTECTED]> wrote: > > > > >Hi Patrick, > > > > > >I think the Format function considers "1:00" to be a string and > > subsequently can't match with the formatting defined by "hh:mm tt" > > > > > >try this: > > > > > >Format(CDate("1:00"), "hh:mm tt") > > > > > >cheers, > > >mw > > > > > >> -----Original Message----- > > >> From: Patrick Burrows [mailto:[EMAIL PROTECTED]] > > >> Sent: Monday, 27 May 2002 11:53 AM > > >> To: [EMAIL PROTECTED] > > >> Subject: [DOTNET] VB.NET Oddity > > >> > > >> > > >> Can anyone explain to me these results in VB.NET: > > >> > > >> ?Format("1:00", "hh:mm tt") > > >> "hh:mm tt" > > >> > > >> I am expecting it to be "1:00 am" > > >> > > >> I can get named formats to work ("Medium Time") but not any > > >> custom formats. > > >> > > >> What am I missing? > > You can read messages from the DOTNET archive, unsubscribe > from DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
