Hello Martijn,
Glad to see you again.
As for the resource based localization feature in .net framework, it
support programmatic resource management or declarative management.
Therefore, for your scenario, whether we can play with centralized
localization resource also depend on how to peform the localization task in
our application.
** If your application will programmtically load resx file or resource
file(binary format), you can consider put those resource files in a central
place(shared place) and programmtically access that directory for resource
files in your application code(you can configure this central directory
path as a entry in the application's web.config file)
ResourceManager.CreateFileBasedResourceManager method will help create
resouce manager from a specify file location.
http://msdn2.microsoft.com/en-us/library/system.resources.resourcemanager.cr
eatefilebasedresourcemanager.aspx
** If your application is using the declarative resoure management(such as
the new Localized page feature in ASP.NET 2.0 and specify localization
property in aspx template ....), I'm afraid we have to put the resoruce
files(resx or resource or satellite assembly) in the application's private
bin dir (or GAC if strong-named).
BTW, generally, for an application, you will use resx file to store
application resources and compile it into satellite assemblies. Therefore,
when the the resource should be updated, we just recompile them to generate
the new satellite assembly and redepoy the satellite assemblies.
#Packaging and Deploying Resources
http://msdn2.microsoft.com/en-us/library/sb6a8618.aspx
Please feel free to let me know if you have any questions on this or if
there is anything else we can help.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
