In Web sites with local resources, local resources are ordinarily treated as Web UI content. However, the merge tool does not process the local resources because local resources by their nature are already folder specific.
If the original site contains local resources, the local resources are not touched by the merge process, because it is not possible to merge local resources into a large resource assembly. Similarly, global resources are not merged.
For that you have to run aspnet_merge with - w option which will merge only the web content precompiled assemblies. In this case the precompiled assemblies like:-
App_Code.dll, App_global.asax.dll, App_GlobalResources.dll remains untouched by the merge process. Otherwise if we use the -o switch instead of -w, all the assemblies including above specified assemblies will be merged, that will make stop working culture information which is folder specific and will not find the App_GlobalResources.dll.
*A satellite assembly is defined as an assembly with resources only, no executable code!
References:-