resx

I'm getting a dozen "Invalid Resx file. ResX input is not valid. Cannot find valid "resheader" tags for the ResX reader and writer type names." err msgs on trying to compile. I had this problem before, as can be seen here . This time, though, it manifests itself a little differently. First, here is what I did: I selected the context menu item "Undo Pending Changes" on several files in a project. For each of them, their related *.resx file apparently got corrupted. 2-clicking the first err msg in the Error List takes me here in the .resx file: <resheader name="resmimetype"> <value>text

I'm using dataannotations in an MVC2 app and am a little discouraged when trying to use RESX file resources for error messages. I've tried the following but keep getting the exception "An attribute argument must be a constant expression, typeof expression or array creation expression of an attribute parameter type" [Required(ErrorMessage = Resources.ErrorMessages.Required)] [Required(ErrorMessageResourceName = Resources.ErrorMessages.Required, ErrorMessageResourceType = typeof(Resources.ErrorMessages)] I keep getting that error message unless I replace ErrorMessageResourceName with "Required"

I have Resources.resx, which is used to generate Resources.designer.cs. Should Resources.designer.cs be checked in, or can I rely on Visual Studio generating it when required? My preference is: If it's modified by the build system, ensure the build process will create it and don't check it in. For autogenerated files like 'designer', I check them in. They only get modified when other components get changed (by me). It's generated by VS and not modified by the build system. I ran across your post for a problem I am experiencing, not quite the same, but it helped me find a temporary solution.

Resource files seem great for localization of labels and messages, but are they perfect? For example: Is there a better solution if there is a huge amount of resources? Like 100,000 strings in a .resx file? (Theoretically, I do not actually have this problem) Is this a good method for storing the other types of data, such as images, icons, audio files, regular files, etc.? Is it a best practice to store your .resx files in a stand-alone project for easier updates/compiling? Are there any other issues that you have run into when using .resx files? 1. Is there a better solution if there is a

At my office, we have had a long-standing debate about Localization/Globalization and how to handle it. One side pushes for the Resource (.resx) file route built in to ASP.NET, one side pushes for a database driven solution. A third group believes in rolling a custom solution. Of course, each method has its own unique benefits and disadvantages - and we've discussed it over and over, without ever coming to a real consensus. So, I pose it to the community: in your experience, which method provides the best mix of the following as the application grows: Maintainability Extensibility Performance

I am starting a new application in WPF and I am curious how to handle Localization? In WinForms you can use resx strings for the UI text, how is this done in WPF? Is there a special binding syntax for binding to resx resources or is there a different way of doing this? Thanks! Madeleine Check out WPF Globalization and Localization Overview . The article explains nicely how localization in WPF works. you can use a MarkupExtension to do localization with dynamic language switching. Here is an interesting article about this: http://www.wpftutorial.net/LocalizeMarkupExtension.html I found very

We use resx files to localize our web applications. We usually create local resx files (that map to a specific page) when only one page uses a certain phrase, and a global resx file when more than one page needs the phrase. But the good thing about global resx files is that they are a class, and you can call the phrases like you call properties of a class: Resource.UI.iNotFound So I was thinking - why have local resx files at all? why not use one global resx file for the whole application, and that way avoid runtime errors from calling non-existent phrases? I'm sure there's a good answer for

I am trying to get the localization for my MVC project working with our existing infrastructure for editing string resources. We store all our resource string in database tables and have a front end web UI to edit them with, and an export application which generated the .resx files. This all works great, but I am having a little difficulty with a new project using MVC2 and VS2010. I have asked another question on this, the answer to which almost got me there, but not quite. I have now changed the resources to be in a Resources folder (instead of App_GlobalResources), as recommended by a number