Sorry meant the culture entries. AFAIK the best way to control is those
specific files (web.config for a single app, machine.config for all ASP.NET
sites) so that you do'nt have any more to deal with control panel
settings...
See aroound
http://msdn.microsoft.com/library/de...balization.asp
for details...
Patrice
--
"Stuart" <St****@discussions.microsoft.com> a écrit dans le message de
news:79**********************************@microsof t.com...
Hi
globalization requestEncoding="utf-8" responseEncoding="utf-8" /
I did not expect this to be aproblem as it works on one and not the
other....but please tell me if I am wrong
Thanks for your help
"Patrice" wrote:
What do you have in the globalization section of your web.config file ?
Patrice
--
"Stuart" <St****@discussions.microsoft.com> a écrit dans le message de
news:13**********************************@microsof t.com... Hi There
Probably missing something drastically obvious here....
I have just moved an .asp application from a test IIS server to a
running IIS server and have become confused... I am using format(blah blah,
"c").ToString
From what I can see both servers are configured exactly the same as
far as regional settings are concerned - however, the new server insists on
showing currency symbol as $ and is also showing the date in an unusual format
What am I missing ?
Thanks