Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
SignalR Blueprints

You're reading from   SignalR Blueprints Build real-time ASP.NET web applications with SignalR and create various interesting projects to improve your user experience

Arrow left icon
Product type Paperback
Published in Feb 2015
Publisher
ISBN-13 9781783983124
Length 244 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Einar Ingerbrigsten Einar Ingerbrigsten
Author Profile Icon Einar Ingerbrigsten
Einar Ingerbrigsten
Arrow right icon
View More author details
Toc

Table of Contents (12) Chapters Close

Preface 1. The Primer FREE CHAPTER 2. Overheating the Discussion 3. Extra! Extra! Read All About It! 4. Can You Measure It? 5. What Line of Business Are You In? 6. An Architectural Taste 7. The Three Screens – Mobile First 8. Putting the X in .NET – Xamarin 9. Debugging or Troubleshooting 10. Hosting and Deployment Index

Convention over configuration


Often established in projects are ways of doing things, recipes that we follow every time we implement certain aspects of our systems. These can often be automated and put to work as conventions. A good example of this is the configuration of the relationship between an interface and its implementations. One convention that you might find is that the ISomething interface has a default implementation called Something. The convention here is that the class implementing the interface has the same name without the prefix: I. This particular type of convention is something some people consider as anti-pattern, but personally, I don't. There are some discussions that say a better convention would be to drop the I prefix for the namespace and instead add the Impl postfix on the implementation. In this chapter, we'll see a convention used for views and ViewModels, stating that they go in pairs as long as they have the same name but a different extension (such as.html...

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