Databases
StackOverflow2013
Postsdbo
POHow do I get the Localizable property and support in my own design tool?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow do I get the Localizable property and support in my own design tool?
    text
    copied!<h3>Overview</h3> <p>In another question, I asked about <a href="https://stackoverflow.com/questions/205138/globalizing-runtime-generated-assemblies">deploying localizations for some runtime compiled <code>UserControl</code>'s</a>. However, before I can get to deploying the localizations, I need a way of localizing the controls.</p> <h3>Background</h3> <p>The controls are created by our own WinForms-style designer (using .NET's support for design surfaces, etc.) and saved as a binary format that combines the <code>CodeCompileUnit</code>, resource resx, and user source into one file. These files are then compiled into an assembly as appropriate at runtime by another tool.</p> <p>In order to localize these, we need to tell the designer and serialization that localizable property values are to be stored in the resources. The VisualStudio WinForms designer does this using an extension property called <code>Localizable</code> and an associated property for specifying the default culture. We need this property in our custom designer, if possible.</p> <h3>Constraints</h3> <p>We need our standalone designer tool that is easy to use for non-developer types as well as restricting certain actions so using a free edition of Visual Studio (i.e. C# Express) is not going to work (I've already pitched it and failed); therefore, any solution to how we localize these UserControl's needs to compensate for this.</p> <h3>Question</h3> <p>Can we get the Localizable support into our custom WinForms designer?</p> <ul> <li>If yes, how?</li> <li>If no, what alternatives are there to localizing our <code>UserControl</code>'s? e.g. post-processing somehow, different file format, etc.</li> </ul>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload