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 3798742
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 19, 20262026-05-19T13:37:17+00:00 2026-05-19T13:37:17+00:00

Is there any benefit to doing the following: public class Foo { private Bar

  • 0

Is there any benefit to doing the following:

public class Foo
{
    private Bar bar;

    public Foo()
    {
        bar = new Bar();
    }
}

Instead of doing it like so:

public class Foo
{
    private Bar bar = new Bar();

    public Foo()
    {
    }
}

Given that at instantiation, the private member variable in either example will be instantiated, I don’t believe there is a difference, but I’ve seen it enough times to where I’m curious.

  • 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-19T13:37:18+00:00Added an answer on May 19, 2026 at 1:37 pm

    In the exact case you’ve given, there isn’t a difference – but in general there is.

    Variable initializers are executed before the base class constructor is called. If that base constructor calls a virtual method which uses some of the instance variables, you can see that difference.

    For spec fans, it’s in section 10.11.2 of the C# 4 spec:

    When an instance constructor has no constructor initializer, or it has a constructor initializer of the form base(…), that constructor implicitly performs the initializations specified by the variable-initializers of the instance fields declared in its class. This corresponds to a sequence of assignments that are executed immediately upon entry to the constructor and before the implicit invocation of the direct base class constructor.

    Here’s an example demonstrating this:

    using System;
    
    public class Base
    {
        public Base()
        {
            Dump();
        }
    
        public virtual void Dump() {}    
    }
    
    class Child : Base
    {
        private string x = "initialized in declaration";
        private string y;
    
        public Child()
        {
            y = "initialized in constructor";
        }
    
        public override void Dump()
        {
            Console.WriteLine("x={0}; y={1}", x, y);
        }
    }
    
    class Test
    {
        static void Main(string[] args)
        {
            new Child();
        }
    }
    

    Result:

    x=initialized in declaration; y=

    Now having said the above, I would try hard to avoid calling virtual methods from a constructor. You’re basically asking the derived class to work in a partially-initialized fashion. However, it’s a difference you should be aware of.

    As for where to initialize variables… I have to admit I’m not particularly consistent, and I don’t find that’s actually a problem. If I have any specific bias, it’s probably to initialize anything which won’t depend on any parameters at the point of declaration, leaving the variables which I can’t initialize without extra information to the constructor.

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

Sidebar

Related Questions

assuming x is an object... Is there any benefit of doing: if (typeof x.foo
I am working on a new project. Is there any benefit with going with
Do I really get any benefit out of doing the following (as opposed to
I'm wondering why List<T>.ForEach(Action<T>) exists. Is there any benefit/difference in doing : elements.ForEach(delegate(Element element){
Is there any benefit in using a <blockquote> element over a <div> ? I
Is there any benefit on Windows to use the WSA winsock functions compared to
Is there any benefit in using compile for regular expressions in Python? h =
I there any benefit to putting the javascript references in individual pages vs the
In asp.net is there any benefit to including or not including an id property?
When using Google app engine is there any benefit to use a CDN if

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.