No problem. There could be a legitimate reason why it's coded the way it is. I often learn a lot when I ask these types of questions.

>The refresh routine isn't the point of the application, so it was done quick and dirty. I had a comment explaining such further into the loader. I'll pull it up a bit.
>
>>

>>public ActionResult Refresh()
>>        {
>>            var movies = MovieLoader.LoadMovies();
>>
>>
>>            _dataContext.ProductionCompanyMovies.Delete();
>>            _dataContext.MovieGenres.Delete();
>>            _dataContext.Characters.Delete();
>>            _dataContext.Actors.Delete();
>>            _dataContext.Movies.Delete();
>>            _dataContext.Genres.Delete();
>>            _dataContext.ProductionCompanies.Delete();
>>            _dataContext.MovieStatuses.Delete();
>>            _dataContext.SaveChanges();
>>            movies.ForEach(movie => _dataContext.Movies.Add(movie));
>>            if (_dataContext.MovieStatuses.All(status => status.Status != "Cancelled"))
>>            {
>>                _dataContext.MovieStatuses.Add(new MovieStatus("Cancelled"));
>>            }
>>            if (_dataContext.MovieStatuses.All(status => status.Status != "Planned"))
>>            {
>>                _dataContext.MovieStatuses.Add(new MovieStatus("Planned"));
>>            }
>>            if (_dataContext.MovieStatuses.All(status => status.Status != "In Production"))
>>            {
>>                _dataContext.MovieStatuses.Add(new MovieStatus("In Production"));
>>            }
>>            _dataContext.SaveChanges();
>>
>>
>>            return new HttpStatusCodeResult(HttpStatusCode.OK);
>>        }
>>

>>
>>The strings in
>>

>>new MoveStatus("magic string")
>>
>>status.Status != "In Production"
>>

>>
>>
>>>Where exactly is this magic string you speak of?