Book Image

ASP.NET MVC 4 Mobile App Development

By : Andy Meadows
Book Image

ASP.NET MVC 4 Mobile App Development

By: Andy Meadows

Overview of this book

The ASP.NET MVC 4 framework is used to build scalable web applications with the help of design patterns and .NET Framework. The Model-View-Controller (MVC) is a design principle which separates the components of a web application. This separation helps you to modify, develop, and test different components of a web application. ASP.NET MVC 4 Mobile App Development helps you to develop next generation applications, while guiding you to deal with the constraints the mobile web places on application development. By the end of the book, you will be well versed with all the aspects of mobile app development. ASP.NET MVC 4 Mobile App Development introduces you to developing mobile web apps using the ASP.NET MVC 4 framework. Walking you through the process of creating a homebrew recipe sharing application, this book teaches you the fundamentals and concepts relevant to developing Internet-ready mobile-enabled web apps. Through the sample application, you will learn how to secure your apps against XSS and CSRF attacks, open up your application to users using third party logins such as Google or Facebook, and how to use Razor, HTML 5, and CSS 3 to create custom views and content targeting mobile devices. Using these custom views, you will then learn how to create web apps with a native mobile device feel using jQuery mobile. By the end of the book, you will be presented with a set of challenges to prove to yourself that you now have the skills to extend your existing web applications to the mobile web or create new mobile web apps.
Table of Contents (23 chapters)
ASP.NET MVC 4 Mobile App Development
Credits
About the Author
Acknowledgment
About the Reviewers
www.PacktPub.com
Preface
7
Separating Functionality Using Routes and Areas
Index

The BrewHow model


The Entity Framework supports three distinct ways to model our data: Database First, Model First, and Code First.

  • Database First is used when the database already exists and provides support to derive a model from the existing database schema

  • The Model First approach provides support to visually model our data and, from the model, generate the database

  • Code First allows us to generate our database schema from a model we define in code

Since we are developing a new app, the Database First method of modeling our data doesn't really apply. The Model First approach, introduced in Visual Studio 2010, could be used for the BrewHow app, but we will instead opt for the more agile approach of Code First.

The Code First approach will also allow us to update the schema in a (largely) non-destructive manner using migrations. This is important since we will adjust the model to better map our domain as we continually enhance our app. Additionally, it's just cool and we like new shiny toys...