Geek Answers Handbook

ASP.NET: explicit vs implicit localization?

In my opinion, the advantage of implicit localization over explicit localization is that if you have several properties for localization for a given control, this is a more economical syntax.

In the case where you just need to localize some text, I use the asp: Localize control, which has only one property (Text), which is displayed in the user interface. Is there a reason to use one over the other? Any style of preference? Are there any differences in speed?

Implicit

<asp:Localize ID="Localize1" runat="server" meta:resourcekey="Something" />

against

Explicit

 <asp:Localize ID="Localize1" runat="server" Text="<%$ Resources:Something %>" />
+6
explicit implicit localization asp.net-controls
source share
2 answers

I am more of an Explicit supporter, sometimes you need to encode / decrypt what you localized. In addition, when dealing with multiple languages ​​and cultures, using Explicit saves you headaches.

+1
source share

Well, your question made me wonder if any of them would provide runtime error checking. And I found that the dose does not provide compile-time verification. Both bombs at runtime for given incorrect values.

0
source share

More articles:


All Articles