Articles with this tag assume an intermediate knowledge within this category.
Dropdown Filter on Multiple Columns In my Telerik: Dropdown with Template article (link), I demonstrated how to configure a dropdown to display choices with multiple columns. The dropdown provides a powerful and intuitive filter feature which by default allows the user to filter choices based on what they type into the filter textbox. In this…
Using Custom Validation on Model Properties While ASP.NET MVC provides powerful native validation, some requirements require custom routines to ensure certain model data is valid. In this artilce I’ll demonstrate how to configure a model for custom validation and provide a simple example function. First, I’ll decorate the model property with an attribute of the…
Please see my other Web articles. Miscellaneous Visual Studio: Publishing Profile
Please see my other AJAX articles. Using AJAX to update a table from a dropdown In this article I’ll demonstrate using AJAX to update an HTML table based on a dropdown selection. First I’ll define the ViewModel to contain data for this exercise. Next, I’ll define the dropdown to be populated. Now, I’ll populate the…
Please see my other Web articles. This page demonstrates some of my AJAX skills in delivering server-side functionality to the client. AJAX Dropdown Update Table
Please see my other Web articles. This page demonstrates some of Telerik’s impressive suite of rich controls designed to empower users, increase productivity and streamline business processes. Telerik UI for ASP.NET MVC Display Dynamic Instructions Dropdown Filter on Multiple Columns Dropdown with Template Grid-Dropdown Column Filter Grid-Display Success/Failure Notification Grid-Dropdown Grid-Editor Template
Avoiding Dependencies Between Layers As part of the S.O.L.I.D. design principles, the Dependency Inversion Principle (DIP) provides guidance for ensuring layers within the application avoid unnecessary dependencies from coupling. DIP ensures each layer’s modules remain independent of one another and should depend on abstractions instead of concrete details, increasing usability and flexibility to change. In…
Providing Focused Behaviors for Classes As part of the S.O.L.I.D. design principles, the Interface Segregation Principle (ISP) supports other S.O.L.I.D. principles in providing classes with focused behavior by ensuring interfaces inherited by classes remain lean and focused on specific behaviors. To illustrate ISP, I’ll use examples from the Single Responsibility Principle (SRP) article. I’ll begin…
Keeping Class Behavior Focused As part of the S.O.L.I.D. design principles, the Liskov Substitution Principle (LSP) ensures when designing classes, the user interface must operate by contact by ensuring during run-time, each object should be replaceable by objects instantiated by a subtype of that class or vice versa. For example, subtype classes (derived) must not…
Supporting Change Without Breaking Software As part of the S.O.L.I.D. design principles, the Open–Closed Principle (OCP) ensures parts of software (classes) are open for extension, but closed for modification. In other words, you should be able to modify a class’ behavior without modifying its code. New methods are added by adding new classes without changing…
