How can I temporarily diable localization...

[jojobar]

Hello,

I am trying to localize an existing application (asp.net 2.0). using
implicit as well as explicit localization.

Asp.net 2.0 uses App_LocalResour ces folder for implicit localization. When
this happens the tag values for Text, ToolTip etc. are not used from the aspx
file but read from the resource files. The problem is that most developers
works
on the aspx files to make and view changes.

We would like to have our developers work and test in aspx files and then we
would like to write a program to synchronize the text values from the aspx
files to the resource files (.resx files) later during the release.

Is it possible to temporarily switch off the globalization in asp.net 2.0
using some settings in web.config, or writing some C# program in
global.asax.cs. When the switch is off, I would like asp.net to work as if
there are no globalization resources (i.e. it should read text values from
aspx files and not the resource files).

Any input will be appreciated.

Thanks
--
-jojobar

[Steven Cheng[MSFT]]

Hello jojobar,

Welcome to the ASPNET newsgroup.

From your description, you're developing an ASP.NET 2.0 web application
which use the "Local Resource" to localize all the pages in the
application. Currently you're wondering whether we can temporarily disable
using "Local Resource" and instead use the aspx template's setting for
those pages which is configured to use "Local Resource", correct?

Based on my research, when page is configured to use "Local Resource", the
localized controls are associated to their localized resource items by the
"meta:XXX" attributes, therefore, if we want to prevent the controls from
getting property values from "Local Resource" files, we have to remove the
"meta:XXX" attributes. There is no other attributes at page level or
application level which can disable the "Local Resource" setting(if the
page or control has used the "meta:xxx" attribute).

In addition, for your scenario, would you consider put all the test control
properties in the default "Local Resource" file at development time? Since
we can control the page or application to use a fixed culture/uiculture
setting, by put the test control property values in a certain culture's
"Local Resource" file, the pages can always read property settings from
that specific file.

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

[jojobar]

Thank you for your reply. I kindof figured this out after doing some
research. It would be nice to be able to do this though!
--
-jojobar
"Steven Cheng[MSFT]" wrote:

Hello jojobar,

Welcome to the ASPNET newsgroup.

From your description, you're developing an ASP.NET 2.0 web application
which use the "Local Resource" to localize all the pages in the
application. Currently you're wondering whether we can temporarily disable
using "Local Resource" and instead use the aspx template's setting for
those pages which is configured to use "Local Resource", correct?

Based on my research, when page is configured to use "Local Resource", the
localized controls are associated to their localized resource items by the
"meta:XXX" attributes, therefore, if we want to prevent the controls from
getting property values from "Local Resource" files, we have to remove the
"meta:XXX" attributes. There is no other attributes at page level or
application level which can disable the "Local Resource" setting(if the
page or control has used the "meta:xxx" attribute).

In addition, for your scenario, would you consider put all the test control
properties in the default "Local Resource" file at development time? Since
we can control the page or application to use a fixed culture/uiculture
setting, by put the test control property values in a certain culture's
"Local Resource" file, the pages can always read property settings from
that specific file.

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

[Steven Cheng[MSFT]]

Thanks for your quick response.

Yes, I think this is a reasonable suggestion. You can also try posting it
in the MSDN feedback center to suggest such a feature:

http://lab.msdn.microsoft.com/produc...k/default.aspx

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)