Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Subclasses:</p> <pre><code>[STAThread] static void Main() { // just some example code to show it working in winforms, but // anything using System.ComponentModel should see the change Application.EnableVisualStyles(); Application.Run(new Form {Controls = {new PropertyGrid {Dock = DockStyle.Fill, SelectedObject = new Foo()}}}); } class Foo { // assume the following literals are keys, for example to a RESX [LocalizedCategory("cat")] [LocalizedDescription("desc")] [LocalizedDisplayName("disp name")] public string Bar { get; set; } } [AttributeUsage(AttributeTargets.Assembly | AttributeTargets.Module | AttributeTargets.Class | AttributeTargets.Struct | AttributeTargets.Enum | AttributeTargets.Constructor | AttributeTargets.Method | AttributeTargets.Property | AttributeTargets.Field | AttributeTargets.Event | AttributeTargets.Interface | AttributeTargets.Parameter | AttributeTargets.Delegate | AttributeTargets.ReturnValue | AttributeTargets.GenericParameter)] class LocalizedDescriptionAttribute : DescriptionAttribute { static string Localize(string key) { // TODO: lookup from resx, perhaps with cache etc return "Something for " + key; } public LocalizedDescriptionAttribute(string key) : base(Localize(key)) { } } [AttributeUsage(AttributeTargets.Class | AttributeTargets.Method | AttributeTargets.Property | AttributeTargets.Event)] class LocalizedDisplayNameAttribute : DisplayNameAttribute { static string Localize(string key) { // TODO: lookup from resx, perhaps with cache etc return "Something for " + key; } public LocalizedDisplayNameAttribute(string key) : base(Localize(key)) { } } [AttributeUsage(AttributeTargets.Assembly | AttributeTargets.Module | AttributeTargets.Class | AttributeTargets.Struct | AttributeTargets.Enum | AttributeTargets.Constructor | AttributeTargets.Method | AttributeTargets.Property | AttributeTargets.Field | AttributeTargets.Event | AttributeTargets.Interface | AttributeTargets.Parameter | AttributeTargets.Delegate | AttributeTargets.ReturnValue | AttributeTargets.GenericParameter)] class LocalizedCategoryAttribute : CategoryAttribute { public LocalizedCategoryAttribute(string key) : base(key) { } protected override string GetLocalizedString(string value) { // TODO: lookup from resx, perhaps with cache etc return "Something for " + value; } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POhow to localize a property description in c#?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMarc Gravell
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POhow to localize a property description in c#?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI must confess that i couldn´t really understand. Is that i.e. "desc" is a key for a localized attribute? How do i access the attribute of a specified property? Could you please adapt your example to mine?
      singulars
      1. PO
      1. US3yanlis1bos
    2. CO@3yanlis1bos in the example I'm using the string as a key only - you would have to fetch out of RESX manually (see the generated file behind the RESX), or use reflection
      singulars
      1. PO
      1. USMarc Gravell
    3. COOk, i think i understood. You`ve extended the descriptionattribute and modified to suit my needs like taking localized strings as input. Is that right? then only thing that i have to do is use the new Attribute instead of old one?
      singulars
      1. PO
      1. US3yanlis1bos
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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