"JamesBV" <NoSpam@telus.net> wrote in message
news:ovj2rv8mvu9rsqu0s0bbj36jg6955q1s6k@4ax.com...
> My PC's Region setting is set to "English (Canada)"... cause I am in
Canada
> (eh?) (: I'm using VB.net, standard edition (v1?)
>
> So I wrote my application based on this Region. I've both Short and Long
> dates being displayed (including a DateTimePicker).
>
> BUT... at work, there are some machines which the Region is the ol'
default of
> "English (United States)".
>
> Canadian:
> Short = dd/MM/yy
> Long = MMMM d, yyyy
>
> USA:
> Short = M/d/yyy
> Long = dddd, MMMM dd, yyyy
>
> What my issue is is that my Date displays (both for long and short) are
either
> OK or Screwed up depending upon the Region display. This because my
labels,
> textboxes, etc. have 'fixed' widths.
>
> Bah! Changing the PC's Regions is NOT an option (I won't go into that).
>
> So how can I have my app display what I want?
>
> I know I can 'build' the date string. Such for a Label, I can have:
> myMonth & myDay & myYear... etc.
>
> But the DateTimePicker is got me stumped.
>
> Prefferably, there must be an easier way to do this so that 'globally' my
app
> works for English (Canadian) and not screw up the Users PC Region setting.
>
> Thanks
>
> James

"JamesBV" <NoSpam@telus.net> wrote in message
news:jet2rvgp3ekp43j1t0b1cuba1kf27n0dlk@4ax.com...
>
> >You can manually set the current thread's UI Culture to whatever you
want.
> >System.Threading.CurrentUICulture (something around there).
>
> Alireza gave me the following:
>
> System.Threading.Thread.CurrentThread.CurrentUICulture = New
> System.Globalization.CultureInfo("en-CA")
>
> Just got to place it, use it properly (of which I have no idea... never
have
> had the 'pleasure' of Threading before) (:
>
> Thanks!
>
> James

"JamesBV" <NoSpam@telus.net> wrote in message
news:ovj2rv8mvu9rsqu0s0bbj36jg6955q1s6k@4ax.com...
> My PC's Region setting is set to "English (Canada)"... cause I am in
Canada
> (eh?) (: I'm using VB.net, standard edition (v1?)
>
> So I wrote my application based on this Region. I've both Short and Long
> dates being displayed (including a DateTimePicker).
>
> BUT... at work, there are some machines which the Region is the ol'
default of
> "English (United States)".
>
> Canadian:
> Short = dd/MM/yy
> Long = MMMM d, yyyy
>
> USA:
> Short = M/d/yyy
> Long = dddd, MMMM dd, yyyy
>
> What my issue is is that my Date displays (both for long and short) are
either
> OK or Screwed up depending upon the Region display. This because my
labels,
> textboxes, etc. have 'fixed' widths.
>
> Bah! Changing the PC's Regions is NOT an option (I won't go into that).
>
> So how can I have my app display what I want?
>
> I know I can 'build' the date string. Such for a Label, I can have:
> myMonth & myDay & myYear... etc.
>
> But the DateTimePicker is got me stumped.
>
> Prefferably, there must be an easier way to do this so that 'globally' my
app
> works for English (Canadian) and not screw up the Users PC Region setting.
>
> Thanks
>
> James

>Why don't you use Formatting?
>
>1. String.Format("mmDDyyyy",myDate)
>2. myDate.ToString("mmDDyyyy")

"JamesBV" <NoSpam@telus.net> wrote in message
news:0us2rvg26qq4tmeh7dmeljbbqu77koddjs@4ax.com...
>
> >Why don't you use Formatting?
> >
> >1. String.Format("mmDDyyyy",myDate)
> >2. myDate.ToString("mmDDyyyy")
>
> Hmmmm... okay. But will this allow me to change the DateTimePicker
display?
> I'm not sure if it will.
>
> I changed my Region Date to USA standard.
>
> I then tried putting MMMM d, yyyy in the Properties "Custom Format"
line...
> and then changed the "Format" line to 'Custom'. But the display still
showed
> USA format.
>
> Other than that... the other stuff (labels, textboxes) work fine.
>
> Idea?
>
> Thanks.
>
> James

>background colour for the text) and I am not surprised if it behaves badly.
>But, I tested that on my machine (UK setting) with "MMMM d, yyyy" in format

>Michael's approach is very professional and polished (he is MVP after all
>;-)):
>System.Threading.Thread.CurrentThread.CurrentUICulture = New
>System.Globalization.CultureInfo("en-CA")

>You can manually set the current thread's UI Culture to whatever you want.
>System.Threading.CurrentUICulture (something around there).

>If you want your whole app to be in a certain culture, you can set the
>thread's culture on startup of your app and leave it.

>requirments, it *probably* won't matter (unless some VP from Korea comes
>over and runs it and it crashes ;)).