Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 4106868
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 20, 20262026-05-20T21:25:55+00:00 2026-05-20T21:25:55+00:00

I have a class that inherits the TextBox Class, call it MyTextBox I’d like

  • 0

I have a class that inherits the TextBox Class, call it MyTextBox

I’d like to redefine the default Background value for this class.

So I looked for a way to do so and found a good option: call BackgroundProperty.OverrideMetadata()

trouble is: where can I put this?

in the App.OnStartup()? Ugly and not practical, I’d like that to be in my Class’s code file.

in the Class’s contructor? I get an exception:

PropertyMetadata is already registered
for the type ‘MyTextBox’.

(seems fine to me, I understand why I get this perfectly)

So I looked again a found about the static constructor in C# (did not no about that earlier, what a pity)

so here’s my code:

public class MyTextBox : TextBox
{
    static MyTextBox()
    {
        MyTextBox.BackgroundProperty.OverrideMetadata(typeof(MyTextBox), new FrameworkPropertyMetadata(App.Current.Resources["CustomBackgroundBrush"]));
    }
}

now, I’m pretty happy whith this, but Microsoft isn’t. Namely, when I use the code analysis feature, I get this:

CA1810: Initialize reference type static fields inline

Hence my question: what can I do about it?

  • ignore the warning? >> I don’t like to ignore warnings
  • move the call to the overrideMetadata method? >> I’d like to, but where?

any hints welcome, thanks

Edit: I’ll add that I don’t fully understand why I get this warning, since I am not initializing anything per say in my static constructor, or am I?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-20T21:25:55+00:00Added an answer on May 20, 2026 at 9:25 pm

    Here is the link from MSDN for overridding metadata for overridding metadata for a dependency property:

    It states:
    “Overriding metadata on a dependency property must be done prior to that property being placed in use by the property system (this equates to the time that specific instances of objects that register the property are instantiated). Calls to OverrideMetadata must be performed within the static constructors of the type that provides itself as the forType parameter of OverrideMetadata.”

    And the wording from the link you posted to CA1810 about when to suppress warnings:

    When to Suppress Warnings

    CA1810
    It is safe to suppress a warning from this rule if performance is not a concern; or if global state changes that are caused by static initialization are expensive or must be guaranteed to occur before a static method of the type is called or an instance of the type is created.

    So, your current implementation and suppression of the warning is probably the correct route.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a class that inherits from defaultdict like this: class listdict(defaultdict): def __init__(self):
I have a class Application that my global.asax inherits from. The class has this
I have a class ShipmentsCollection that inherits ObservableCollection which contains shipment objects (entities). This
I have a class that inherits a generic dictionary and an inteface public class
I have a class that inherits from ObservableCollection(Of MyObject) and the MyObject class handles
I have a class A and another class that inherits from it, B. I
I have a class (Descendant1) that inherits from a base class (BaseClass). An instance
if i have a .net 1.1 class that inherits from DictionaryBase and i am
I have a standard windows server that inherits from the ServiceBase class. On the
I have a class that inherits from UIView However when trying to use the

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.