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].
Error. resjson
payPage. resjson
Resources. resjson
Error. resjson
payPage. resjson
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
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:

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.


Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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 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.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…