Loading...
 
Multi-Language Add-In for Visual Studio

Multi-Language Add-In for Visual Studio


Add Resource Key to ASP Project

In my ASP project I have some content that have to be localized that the project scans don’t find (third party controls, other properties than "text" and so on). How can I add those resources to the project? I can add them to the local resx-files no problem. But Multi-Language Add-In will ignore “additional” local resources. So when I export to excel these resources are missing and will not be translated. I tried to add the resources by hand in the project_ml-xml-file (new GeneralId, GeneralText and Property in the correct file), but these entries are thrown away with the next project scan. Am I doing something wrong here? Do I miss something? Why do I need a separate project-file when all the information in overwritten with the next project scan?
Adding additional local resources that the scan don’t find is a must for me. Or can I tune the scan in asp-files?
Uli

Germany

In general, the Add-In will show the properties which have the localizable attribute. For third party controls, it is the responsibility of the author of the control to apply this attribute to properties which may be localized.

My original assumption was, that if this attribute is not present, then it makes no sense to store a resource string for the property, because it will not be loaded anyway. It turns out that this is not entirely true. Sometimes, properties are loaded from resource strings, even without the localizable attribute (but I don't think that they are always loaded for all properties).

To provide a minimal support for this behaviour, there is a special option in the Add-In. Open the Add-In's options dialog (left of the tools icon) and select the "Web" tab. Under "Options for ASP scan" there is an option "Show all text properties".

If you select this option, then the Add-In will simply include all text properties in the grid. The problem is, that it may include junk which you really don't want to see. It may also let you select attributes which really cannot be localized. I don't really like this option.

There is another method, which I am sorry to admit did not work, but which I have just fixed. You mentioned that you can add the resources directly to the local resx files. If you do this, then the Add-In should detect it and show it in the "Additional Resources" tab. This will be included in the Excel export. This did not work in ASP projects, but in version 4.7x.0120 it should work.

By the way, I have tried selecting a ToolTip attribute in a CheckBox control and I had no problem.

Phil


Thank you Phil so far.
The CheckBox thing has to do with this problem I think.

Uli


This version is much better. Sweet.
Thanks a lot!
The last shop stopper is binding issue.
Uli