Great tool, but it would be better not to create localizations in Visual Studio. Using satellite assemblies localization can be created using only .dll/.exe (compiled project).
This way adding a new language does not require recompiling the project. What is more translation could be made even by the end-user.
I found localization tool called LSACreator (http://www.tbs-apps.com/lsacreator - free for non-commercial use or buy option) which does exactly that. It is simple and has same useful features. I am not sure are there any other tools which use only .dll/.exe.
ResXManager is a very powerful tool to localize large solutions with very little effort. When used inside Visual Studio, it gives an excellent overview, where localized texts are still missing, and it allows easy entering of the respective localized texts. It also supports the export of the text strings in Excel tables for external translation. The updated Excel tables can then be reimported to update the solution. I like this tool very much, thanks to the author!
What a great tool. I love it. so productivity-oriented. But, note that there's a bug that you have to open whatever file after installing it in VS. hope it will be fixed. issue: https://resxresourcemanager.codeplex.com/workitem/1374
I've started evaluating this tool for my colleagues and I to use. However, I encountered something a little funny with it - or perhaps related to it.
At least one of our solutions doesn't seem to work with the tool - the resource files are not found. The only thing different between this solution and the ones I've tried where it works (wonderfully!) is that this solution was created in Visual Studio 2010 *SP1* and the others with the RTM version. I also note (since it seems important) that the display of properties on the .resx file mentions that a custom tool was used - which I thought was the default one: ResXFileCodeGenerator
Is there any thing to these observations? Otherwise, what would prevent ResXManager from working on these files?