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 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 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.


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 aboveWhen 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 implementation is n…

Task based Asynchronous pattern, Async & Await and .NET 4.5

One of the key features in .Net 4.5 is to write asynchronous programs much easier. So if I was to write asynchronous programs in .Net 2.0/3.5, I would either follow the event based model or the callback based model. For an example, a synchronous method that does intensive work (say the DoWork()) can be made asynchronous by using the following patterns
1) Implementing the IAsyncResult pattern. in this implementation, 2 methods are exposed for the DoWork() synchronous method, the BeginDoWork() and the EndDoWork() method. The user will call the BeingDoWork() passing in the required parameters and a callback of the delegate type AsyncCallback(IAsyncResult). The BeginDoWork() will spawn a new thread a return control back to the user. Once work is completed in the spawned method, as a last step, it will call the inform the AsyncResult implementation, which in turns will call the EndDoWork() (which is the callback that was passed in to the BeginDoWork()).
2) Implementing the event pattern. Her…

MEF (Managed Extensibility Framework), .NET 4, Dependency Injection and Plug-in Development

Almost after .Net 4 was released I remember reading about MEF (Managed Extensibility Framework), this was a framework for developers to compose their application with required dependencies. At first this looks like the Unity Container used for dependency injection, but MEF is much more than a dependency container but there is nothing stopping you from using MEF as a dependency injector.I remember around 5 years back when I was in a project that created a framework that allows developers to plug-in there modules as WinForm screens. The developer would create a set of screens with the intended functionalities and the drop this component in the bin folder of the framework and then will move on to do some painful configurations for the framework to pick up the module. Dropping the component into the bin folder and doing a bit of configuration is all that s needed for the framework to pick up display the screens. Typically, the configurations would also contain metadata about the screen.Al…