Skip to main content

ASP.NET Localization - Implicit Resource Assignment


In one of my previous post I talked about ASP.NET localization basic and 2 ways of which resources can be assigned to ASP.NET pages and controls were also discussed.
In this post I will talk about a powerful ASP.net feature that can be used to assign resources implicitly.
This feature can be used to assign multiple resources to a control at one shot without individually assigning resources.

Lets take an example to demonstrate this, I am going to place a simple button control on a page.
Now I want assign 3 types of resources, the Text, Color of the button and the tooltip of the button.
This is my resource file.

I have assigned values for all fields that I require. Note how the key has been named, that is a prefix followed by a period and then followed by the property of the control that I need to assign these resources too, for an example "button" is my prefix followed by a period and then the "Text" property.

Now, in my ASPX page all I have to do is this.
Note that without assigning resources to individual properties I add a meta:resourcekey attribute, and I pass the prefix as the value for this attribute.

In the background ASP.NET will collect all the resource keys for this page and then filter out the ones that contain the prefix "button" and then for each of these filtered key, it will see if the suffix matches a property in the control if so it will assign the resource value to that property.

For an example in our example the initial filtered list will contain 3 keys, "button.Text", "button.Tooltip" and "button.BackColor", now we have assigned this meta tag to the button control, so ASP.net will see if the suffix matches the properties of the button control, the suffix of the first key is Text, so the resource value for the key "button.Text" will be assigned to the text property of the button, next Tooltip is also a property of the button so that resource value for the key "button.Tooltip" will be assigned to the button's tooltip.

The advantage of using the meta:resourcekey as you can see is that you can assign multiple resources to properties to in one shot implicitly.

Comments

Popular posts from this blog

Hosting WCF services on IIS or Windows Services?

There came one of those questions from the client whether to use II7 hosting or windows service hosting for WCF services. I tried recollecting a few points and thought of writing it down. WCF applications can be hosted in 2 main ways - In a Windows service - On IIS 7 and above When WCF was first released, IIS 6 did not support hosting WCF applications that support Non-HTTP communication like Net.TCP or Net.MSMQ and developers had to rely on hosting these services on Windows Services. With the release of IIS 7, it was possible to deploy these Non-Http based applications also on IIS 7. Following are the benefits of using IIS 7 to host WCF applications Less development effort Hosting on Windows service, mandates the creating of a Windows service installer project on windows service and writing code to instantiate the service, whereas the service could just be hosted on IIS by creating an application on IIS, no further development is needed, just the service implementa

The maximum nametable character count quota (16384) has been exceeded

Some of our services were growing and the other day it hit the quote, I could not update the service references, nor was I able to run the WCFTest client. An error is diplayed saying " The maximum nametable character count quota (16384) has been exceeded " The problem was with the mex endpoint, where the XML that was sent was too much for the client to handle, this can be fixed by do the following. Just paste the lines below within the configuration section of the devenve.exe.config and the svcutil.exe.config files found at the locations C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE , C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin Restart IIS and you are done. The detailed error that you get is the following : Error: Cannot obtain Metadata from net.tcp://localhost:8731/ Services/SecurityManager/mex If this is a Windows (R) Communication Foundation service to which you have access, please check that you have enabled metadata publishing at the specified address. F

ASP.NEt 2.0 Viewstate and good practices

View state is one of the most important features of ASP.NET because it enables stateful programming over a stateless protocol such as HTTP. Used without strict criteria, though, the view state can easily become a burden for pages. Since view state is packed with the page, it increases size of HTTP response and request. Fortunately the overall size of the __VIEWSTATE hidden field (in ASP.NET 2.0) in most cases is as small as half the size of the corresponding field in ASP.NET 1.x. The content of the _VIEWSTATE field (in client side) represent the state of the page when it was last processed on the server. Although sent to the client, the view state doesn't contain any information that should be consumed by the client. In ASP.NET 1.x, if you disable view state of controls, some of them are unable to raise events hence control become unusable. When we bind data to a grid, server encodes and put whole grid in to view state, which will increase size of view state (proportional to the