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

Chapter 7. Separating Functionality Using Routes and Areas

Think about all of the URLs that begin with facebook.com or twitter.com. Think about the MSDN section of Microsoft's site. Imagine if you had to maintain controllers and actions to handle every single piece of content returned from those sites. It's pretty safe to say the task is beyond daunting, it's pretty much impossible.

While we would be exceptionally fortunate to have to deal with those problems in something we create, odds are we will never have to concern ourselves with scalability and functionality on that scale. That doesn't mean our app will never cross some maintenance threshold. When it does, we may decide we need to separate it into different logical divisions. We may choose to do so because our app has become too big or too complex to have every controller sitting within the Controllers folder. Sometimes it's just wanting the URLs of our app to be simple, meaningful, and RESTful.

In this chapter, we are going to work...