Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

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

Jake Ford
Jake Ford
9,230 Points
Posted by 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
231,198 Points
Steven Parker
Steven Parker
231,198 Points

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

Jake Ford
Jake Ford
9,230 Points
Jake Ford
Jake Ford
9,230 Points

Just updated, sorry Steven

1 Answer

Steven Parker
Steven Parker
231,198 Points
Steven Parker
Steven Parker
231,198 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.