![]() In practice, however, you most likely will be moving those items to another place in the project structure, which may be a. In theory, this is so you can place items like Entity Framework data contexts and generated models in this folder. New sample projects often begin with an empty App_Data folder. Let's walk through each of these folders and files and see if we can determine which ones we actually need. Here's a screenshot of our default MVC project, and the folders and files it created. ![]() Let's take a look at a default ASP.NET MVC application (created with ASP.NET 4.7 and Visual Studio 2017) and see if we can live without some of the files, folders, and NuGet packages that are included by default. I work mostly in the ASP.NET world, and given that my team is in the process of starting a greenfield project I thought it might be useful to examine a brand-new ASP.NET MVC project with those same two questions in mind. But, given that I live in the real world, that's not possible, so I settle for the best alternative: deleting anything that isn't found to have a reason to exist, often with extreme prejudice. I would much prefer to delete all code ever written, because then it will never break. I examine the item in question and ask myself the following questions: For each file, folder, NuGet package, etc. I have a two-step process that I utilize whenever I have to dive into a code project that I didn't create.
0 Comments
Leave a Reply. |