Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Modern Web Development with ASP.NET Core 3

You're reading from   Modern Web Development with ASP.NET Core 3 An end to end guide covering the latest features of Visual Studio 2019, Blazor and Entity Framework

Arrow left icon
Product type Paperback
Published in Jun 2020
Publisher Packt
ISBN-13 9781789619768
Length 802 pages
Edition 2nd Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Ricardo Peres Ricardo Peres
Author Profile Icon Ricardo Peres
Ricardo Peres
Arrow right icon
View More author details
Toc

Table of Contents (26) Chapters Close

Preface 1. Section 1: The Fundamentals of ASP.NET Core 3
2. Getting Started with ASP.NET Core FREE CHAPTER 3. Configuration 4. Routing 5. Controllers and Actions 6. Views 7. Section 2: Improving Productivity
8. Using Forms and Models 9. Implementing Razor Pages 10. API Controllers 11. Reusable Components 12. Understanding Filters 13. Security 14. Section 3: Advanced Topics
15. Logging, Tracing, and Diagnostics 16. Understanding How Testing Works 17. Client-Side Development 18. Improving Performance and Scalability 19. Real-Time Communication 20. Introducing Blazor 21. gRPC and Other Topics 22. Application Deployment 23. Assessments 24. Other Books You May Enjoy Appendix A: The dotnet Tool

Finding controllers

Regardless of whether you go for POCO or non-POCO controllers, ASP.NET Core will apply the same rules for discovering controllers, which are as follows:

  • They need to have the Controller suffix (strictly speaking, this can be changed, but we will leave this for now).
  • They need to be instantiable classes (nonabstract, nongeneric, and nonstatic).
  • They cannot have the [NonController] attribute applied to them.
  • If they are POCO and do not have the Controller suffix, you can decorate them with the [Controller] attribute.
By convention, the files that contain the controller classes are stored in a folder called Controllers, and also in a Controllers namespace, but this is just ignored.

Controller classes are looked up by the name in the route—the controller parameter—and they are searched in the assemblies registered for that purpose. By default, the currently executing assembly...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image