Skip to main content

Where we can add resjson files in a Metro Application

In one of my latest post I wrote a short introduction about how we can support localization in a Metro Application for Windows 8. The current framework for Metro Application makes a great job. Today I want to discuss about resjson files.
This new extension was introduce with Metro Applications and help us to store all the strings that are localized in a very simple format (key, value) using json. In this case json is better than XML (when json is not better).
By default, when we create a Metro Application, a folder named strings is created in the root of our project. Under this folder we can create us many folders we want with a name convention [cultureName]-[regionName].
string
en-US
Resources.resjson
Error. resjson
payPage. resjson
en
Resources. resjson
Error. resjson
payPage. resjson
fe-BE
Resources. resjson
Error. resjson
payPage. resjson
I have the following question for you: How many strings folders can we have in an application? Does the resjson files need to be under the strings directory?
Basically, the strings folder is only a convention; we can have the resjson files under any directory structure. To be able to load the content from these files, the framework needs two important things:
Each resjson file need to have the “Content type” property set to “Resource”. This property can be accessed from the “Properties” tab of Visual Studio.
Each resjson file need to be under a folder that specifies the culture and/or region with the following format
 [cultureName]-[regionName]
If we respect these conventions, the framework will be able to load all this resources without any problem. Because of this we can end with a custom folder structure like this:
myProject
payment
pages
payPage
payPage.html
payPage.css
payPage.js


resources
en-US
pages.resjson
errors.resjson
What we need to remember: We can have resjson file under any directory in our project. The only thing that we need to have is the parent directory of the resjson file in the custom format to specify the culture and/or region.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too