29.05.2015 Views

o_19mgorv9t13a3ko71fev19l81mqa.pdf

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Figure 2-2. Selecting the initial project configuration<br />

Tip Make sure you select version 4.5.1 of the .NET Framework at the top of the window. This is the latest version of .NET<br />

and is required for some of the advanced features that I describe in this book.<br />

The templates create projects with different starting points and configurations for features such as authentication, navigation<br />

and visual themes. I am going to keep things simple: select the Empty option and check the MVC box in the Add folders and<br />

core references section, as shown in the figure. This will create a basic MVC project with minimal predefined content and will be<br />

the starting point that I use for all of the examples in this book. Click the OK button to create the new project.<br />

Note The other project template options are intended to give you a more complete starting point for your ASP.NET projects. I<br />

don’t like these templates because they encourage developers to treat some important features, such as authentication, as black<br />

boxes. My goal in this book is to give you the knowledge to understand and manage every aspect of your MVC application and, as<br />

a consequence, I use the Empty template for most of the examples in the book – the exception is in Chapter 14, where I show<br />

you the content that the MVC template adds to new projects.<br />

Once Visual Studio creates the project, you will see a number of files and folders displayed in the Solution Explorer window,<br />

as shown in Figure 2-3. This is the default project structure for a new MVC project and you will soon understand the purpose of<br />

each of the files and folders that Visual Studio creates.<br />

31

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!