Note that there are some explanatory texts on larger screens.

plurals
  1. POVS Designer replaces "empty" strings with resource identifier pointing to empty strings
    primarykey
    data
    text
    <p>Weird problem, started with migration to Visual Studio 2010.</p> <p>Some forms, when opened, will have some objects' properties set to a string that is empty in resource file. Most often these are control properties like <code>ImageKey</code>, <code>ToolTipText</code> and for UltraGrid some columns get <code>columnX.Header.Caption</code> set to that string. This will obviously remove set images and give wrong column header texts in other locales. Additionally tooltips will show up in weird places (like tab panel body).</p> <p>This string (strSaveInterestDetails8 below) is empty in Strings.resx (<code>&lt;value /&gt;</code>), but not empty in Strings.fi.resx. When I changed this string to have a space, designer started to use an other "empty" string from Strings.resx..</p> <p>These forms are all derived from common base, but it does not have anything special/suspicious. Debugging these from additional devenv instance failed, since the debugger never broke on the set breakpoints (thrown exceptions in internal VS code were caught).</p> <p>example:</p> <pre><code>ultraGridColumn23.Header.Caption = global::Company.Module.Properties.Strings.strSaveInterestDetails8; ... this._timespanCheck.ImageKey = global::Company.Module.Properties.Strings.strSaveInterestDetails8; ... this.tabPage1.ImageKey = global::Company.Module.Properties.Strings.strSaveInterestDetails8; this.tabPage1.ToolTipText = global::Company.Module.Properties.Strings.strSaveInterestDetails8; </code></pre> <p>So has anyone run into something similar or has better google-fu?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

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