Welcome to the Treehouse Community

The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.

C# ASP.NET MVC Basics Modeling and Presenting Data Updating the Controller

Jake Ford
Jake Ford
9,230 Points

Why not instantiate the repository like this?

Is there a reason to use the constructor rather than do it like so?

private MovieRepository _movieRepository = new MovieRepository();

This code seems to work just as well for me?

Instead of:

        private MovieRepository _movieRepository = null;

        public MovieGalleryController()
        {
            _movieRepository = new MovieRepository();
        }
Steven Parker
Steven Parker
220,634 Points

What's the other way you are comparing this to?

Jake Ford
Jake Ford
9,230 Points

Just updated, sorry Steven

1 Answer

Steven Parker
Steven Parker
220,634 Points

There's no functional difference between these, the reasons for choosing one over the other would depend on the larger context. If you have other needs for a constructor, assigning in the constructor might be more consistent. But otherwise inline initialization could save you from needing an explicit constructor at all.