C#

harold aptroot wrote:

bit of a hack, but you could make an event in the child

mctramp168 wrote:

I remember my colleague I have achieved this funtion in his program,not handling by the system languagepack,He can change the Text property of the button with any name.

/// <summary>
/// This is the original property. We want to 'rename' these in code as well as
/// in the property-editor. First, we'll hide the current property as much
/// as reasonable:
/// </summary>
[Browsable(false)]
public override System.Drawing.Color ForeColor
{
    get
    {
        return base.ForeColor;
    }
    set
    {
        base.ForeColor = value;
    }
}

/// <summary>
/// This is our 'translated' version of the "ForeColor". It gets dumped in the same
/// category as before, but you could also translate that string.
///
/// If you do, a new category will be created automatically, and the property will
/// be visible under that new category-name.
/// </summary>
[Browsable(true), Category("Appearance")]
public System.Drawing.Color VeurgrondKleur
{
    get
    {
        return this.ForeColor;
    }
    set
    {
        this.ForeColor = value;
    }
}

I are troll

George_George wrote:

Any general ideas to debug and analyze further for application hang problem?

Luc Pattyn wrote:

Without trace logs, intermittent or occasional problems are hard to debug, while single-stepping and breakpointing, you are never sure the problem will occur...
With trace logs, you can focus on a bad run; or you can compare traces from a bad run with those from a good run.