CODE Magazine / Articles
Object Oriented Development
Articles filed under Object Oriented Development
Articles
Showing 1–39 of 39
-
Store Application Performance Metadata in a Database Using AOP in ASP.NET Core
Joydip explores programming paradigms (object-oriented, procedural, and aspect-oriented programming) and looks at how AOP (aspect-oriented programming) can help you optimize performance and store performance metadata in a database.
-
Customized Object-Oriented and Client-Server Scripting in C#
You need full control of how your functionality is implemented. Vassili tells you how to use classes and objects for great control, and how to implement them in C# in this article about object-oriented and client-server scripting.
-
Support Your Application Post-Launch Intelligently Using Intercom.io
Updated
Jason shows us how to keep the development team focused on developing while creating built-in post-launch features that keep your users happy too. It’s not magic, it’s Intercom.io.
-
Implementing a Flickr Search iOS Application Using Swift
Updated
Apple’s new language Swift is everywhere these days. Probably the most important app you could build with it is a search engine, and Mohammad shows us how using his own gardening app.
-
Creating Collections of Entity Objects
Updated
Almost every programmer knows (unless you have been living under a rock for the last five years or so) that you should be using classes for all of your programming. You should also be using collections of objects instead of using a Data Reader, a DataSet, or a DataTable in your applications. The reasons for using collections are many and are explored in this article.
-
Understanding Dependency Injection and Those Pesky Containers
We seem to be an industry enamored with buzz words. Even though XmlHttpRequest has been around since the mid-90s, mainstream programmers didn’t give it a second thought until someone attached the term AJAX to it. The same is true for the never-ending quest to put as many different words as we can in front of “driven-development.” Another term that hit the scene in recent years is dependency injection.
-
Smashing the Myth: Why You Must Learn F# - Even If You Aren’t Writing Rocket Science Apps
Updated
If you are a .NET software developer, you have heard of F#. You may have read an article, seen a talk at a user group, or otherwise heard the buzz. However, if those means of reaching you have failed, at the very least, you have noticed it conspicuously appear in the list of languages you can base a solution on in Visual Studio 2010. If you write code on the .NET Framework, you would have to be living under a rock to have not heard of F#.
-
Entity Framework 4.1: Code First
The Entity Framework team at Microsoft has been making several improvements since the launch of v4 with Visual Studio. The biggest of these is the capability to use a Code First or Code Only development model. Previously, if you wanted to work with the Entity Framework, you had to use either a Database First or Model First development model.
-
Post Mortem: Developing the OSS Project AutoMapper
Updated
Jimmy explores what went right and what went wrong with version 1.0 of AutoMapper.
-
POCO Support Comes to Entity Framework 4
When Microsoft first released the Entity Framework, agile developers roundly criticized it. These developers hold the tenets of domain-driven development and testability very high. The classes generated from the Entity Data Model (EDM) are very tightly bound to the Entity Framework APIs by either inheriting from the EntityObject or implement interfaces that allow the classes to participate in change tracking and relationship management.
-
-
Introducing Advanced Code Contracts with the Entity Framework and Pex
Martin introduces Design by Contract and Code Contracts, and gives you a sneak preview of Pex—Microsoft’s new test-suite generator. Along the way, he will show you how to add contracts to ADO.NET entities and some interesting coding strategies, good practices, and pitfalls you may encounter while making a deal with your code.With Code Contracts, Microsoft delivers its own flavor of Design by Contract for the .NET Framework. But wait, what is this thing sometimes called Contract-First Development? How will it change the way you develop software and write your unit tests? And first and foremost, how do you use Code Contracts efficiently?In this article, I will introduce Design by Contract and Code Contracts, as well as give you a sneak preview of Pex-Microsoft’s new test-suite generator. Along the way, I will show you how to add contracts to ADO.NET entities and some interesting coding strategies, good practices, and pitfalls you may encounter while making a deal with your code.
-
Post Mortem Web Project
First Premier Bankcard (www.firstpremier.com) is the 10th largest issuer of Visa and MasterCard credit cards in the United States.First Premier employs multiple thousands of people spread across the state of South Dakota. A major percentage of the employees at First Premier work in call-center operations helping people apply for credit cards.
-
Reinventing Error Handling
Ned introduces the most significant advance in error handling since exceptions and he shows you a new way to look at errors.This article introduces the most significant advance in error handling since exceptions.You get improved tools for today and a glimpse of radical possibilities for tomorrow. You get a framework which supports more expressive error handlers and gives them equal access to error context information. You get a roadmap for adding improved error handling capabilities, including class-level error handlers and the ability to fix errors at run time. Above all, you get a new way to look at errors.
-
S.O.L.I.D. Software Development, One Step at a Time
Derick outlines how to achieve the benefits of low coupling, high cohesion, and strong encapsulation. He also shows how the five S.O.L.I.D. design principles can get you there.Most professional software developers understand the academic definitions of coupling, cohesion, and encapsulation.However, many developers do not understand how to achieve the benefits of low coupling, high cohesion and strong encapsulation, as outlined in this article. Fortunately, others have created stepping stones that lead to these goals, resulting in software that is easier to read, easier to understand and easier to change. In this article series, I will define three of the primary object-oriented principles and show how to reach them through the five S.O.L.I.D. design principles.
-
Bricks and Mortar: Building a Castle
Updated
In an application built with object-oriented techniques, objects are the bricks.You construct little pieces of code encapsulated in these bricks. To build bigger structures, you need to hold these bricks together. You can hardwire them together by instantiating dependent objects within your objects, but it makes the whole structure less flexible in the face of change. So you can adopt an inversion of control (IoC) container to act as your mason to assemble your bricks into complex structures that can flex with changing requirements. In this article, I will examine a popular IoC container, Castle Windsor, and how it enables you to build flexible and robust applications. If you are new to IoC containers and dependency injection, I would recommend reading Martin Fowler's article, Inversion of Control Containers and the Dependency Injection Pattern (http://martinfowler.com/articles/injection.html) and my own article from the March 2008 edition of MSDN Magazine, Loosen Up: Tame Your Dependencies for More Flexible Apps (http://msdn.microsoft.com/en-us/magazine/cc337885.aspx).
-
Beginning Java with NetBeans
This section gets you started quickly with Java programming. First, chapter 1 introduces you to some concepts and terms that apply to Java development. In addition, it shows you how to use the NetBeans IDE to open and run existing projects.
-
Chapter 38: The Payroll User Interface: Model View Presenter
Excerpted from Agile Principles, Patterns, and Practices in C#. As far as the customer is concerned, the Interface is the product.-Jef Raskin
-
Chapter 4 Design Patterns
OOP is a powerful concept that solves many problems found in software development. OOP is not the holy grail of programming, but, as we will see throughout this book, it can help in writing code that is easy to read, easy to maintain, easy to update, and easy to expand.
-
Murach's C# 2012 - Chapter 2
by Joel Murach and Anne Boehm, Published May 2013, ISBN 978-1-890774-72-1 http://www.murach.com/books/cs12/index.htm
-
Objects - Chapter 1
“This excerpt is from the book, ‘Windows 7 Device Driver’ by Ronald D. Reeves, Published Nov 16, 2010 by Addison-Wesley Professional. Part of theAddison-Wesley Microsoft Technology Series series.l, ISBN 139780321670212, Copyright 2011. For more info please visit the publisher site: http://www.informit.com/title/0321670213
-
Working with Objects in Java
Learn how to create objects, test and modify their class and instance variables, call an object’s methods, and convert objects from one class to another.
-
-
Am I a Mad Scientist?
Updated
J. Ambrose Little argues that building an application around a strongly typed, rich domain model—rather than a database-centric or data-set approach—offers real, practical business benefits: easier maintenance, greater code reuse, improved performance, and faster, safer development thanks to compile-time checks and better tooling. He contends that object-oriented design decouples the domain from the database, reduces coupling to UI layers, and enables clearer, more dependable architectures, ultimately making development more enjoyable and less error-prone.
-
Inheritance 101
Updated
Extend your knowledge of inheritance to more easily extend your applications.
-
ASP.NET Development Through Web Controls and Declarative Programming
Updated
ASP.NET WebControls do more than just allow you to write reusable components. They can provide an entire approach to Web application development, allowing you to bring a new level of OOP to the UI and letting you program declaratively.Lately I've come to notice that no other programming term has more definitions than declarative programming. In this article, I will attempt to explain it in terms of how it applies to .NET development, specifically ASP.NET through the use of WebControls. I'll do this by illustrating some real-world examples that I have used in my own projects. In the end, I hope to leave you with an understanding of what declarative programming is, how you can use it when developing ASP.NET Web applications, and how, with the help of WebControls, to use it as an approach to ASP.NET development.
-
Sorting Custom Collections
Have you ever wanted to use a strongly-typed collection to bind your data presentation controls to, only to find that you have very limited sorting capabilities, if any at all?If you are trying to stick to good object-oriented design and shrink the amount of data that you keep in memory, transfer from your data source, or serialize to clients, you likely have run into this situation because you are using strongly-typed collections of your domain objects. So what do you do if you need to sort those collections for presentation or faster searching?
-
'For-Each' Of My Own
The .NET Framework provides many new collection classes that you can iterate (for-each) through.But did you know that you can also iterate through values in any of your classes, not just those that use or inherit from collections?
-
Visualize Your Code with the Class Designer
The Class Designer feature of Visual Studio 2005 allows you to visually manipulate your classes.A picture is worth a thousand words, as the saying goes. The new Visual Studio 2005 (Whidbey) Class Designer provides a visual design environment that allows you to visualize and manipulate your classes. Being able to see your classes and work with them using a visual designer can significantly increase your productivity.
-
Overload Operators to Operate on Your Objects
Updated
Operator overloading provides an intuitive way to support mathematical and comparative operations on your objects.Operator overloading is one of those features that you don't need very often, but when you need it, operator overloading is very nice to have. You will find operator overloading in C# now, but you won't find it in Visual Basic until the upcoming Visual Studio 2005 release.
-
The Power of Inheritance in .NET
ByMarkus Egger
CODE Magazine · 2002 - January/February · VFP Conversion Papers · Markus Egger Talks Tech
Updated
In "The Power of Inheritance in .NET," Markus Egger demonstrates how inheritance in Visual Studio.NET can significantly enhance development efficiency and code quality by enabling reusable, abstract business objects and interface components. He illustrates this with practical examples, showing how subclassing a generic business object simplifies data handling across different entities, and how inheritance facilitates creating customizable ASP.NET and Windows Forms controls. Egger emphasizes the benefits of inheritance beyond basic concepts, encouraging thoughtful class design to leverage its full potential in real-world applications.
-
Understanding Visual Inheritance in .NET
Updated
Markus Egger’s article offers a practical, real‑world tour of visual inheritance in .NET, showing how to design a base data-entry form and create subclassed forms that inherit and extend behavior across languages (C# and VB.NET). He demystifies how inherited forms, controls, and event bindings work, explains the difference between compile-time versus runtime method binding (virtual methods), and demonstrates how to override and invoke base functionality while preserving or extending default behavior. The piece emphasizes pragmatic guidance on scope, protection levels, and multi‑level subclassing, framing inheritance as a simple, powerful tool for maintainable UI design in .NET.
-
The "Basics" of Inheritance
Markus Egger explains that inheritance—soon coming to Visual Basic 7—is a core object‑oriented mechanism that lets developers subclass and extend existing classes (demonstrated with Visual FoxPro examples) to promote reuse, centralized changes, and flexible designs; he covers multilevel vs. multiple inheritance, method visibility (public/protected/hidden), how overriding and DoDefault work, and argues inheritance enables cleaner large‑scale patterns (e.g., strategy) unlike rigid COM interfaces.
-
Where's Your Logic?
Updated
Markus Egger discusses the role of business logic in modern application architecture.
-
-
.NET Interface-based Programming
Updated
In component-based programming, the basic unit of use in an application is a binary-compatible interface.The interface provides an abstract service definition between the client and the object. This is in contrast to the object-oriented view of the world that places the object implementing the interface at the center. An interface is a logical grouping of method definitions that acts as the contract between the client and the service provider. Each provider is free to provide its own interpretation of the interface and its own implementation. To use a component, the client only needs to know the interface definition and have a binary component that implements that interface. This extra level of indirection between the client and the object provides for interchangeability between different implementations of the same interface, without affecting client code.
-
UML Collaboration Diagrams
Updated
In this article, Kevin McNeish highlights the value of UML collaboration diagrams as effective tools for illustrating both the dynamic interactions and static relationships between business objects in software design. He contrasts collaboration diagrams with sequence diagrams, emphasizing their unique ability to visualize object relationships and validate static models. Kevin explains the core elements of collaboration diagrams—objects, links, and messages—and discusses their use in representing complex interactions, including iterations, conditionals, and object state changes. Ultimately, he advocates for collaboration diagrams as a complementary perspective that enhances understanding of object collaborations beyond what sequence diagrams alone can offer.
-
UML Class Diagrams
Kevin McNeish introduces UML class diagrams as essential tools for designing well-structured, maintainable application classes, explaining class notation, visibility, and the key relationships—generalization, dependency, association (including multiplicity, aggregation, composition), and realization—while illustrating how abstract and concrete classes, interfaces, and careful modeling produce flexible, extensible business-object families that form a solid foundation for component-based software.
-
Some Pitfalls of Inheritance
Updated
In "Some Pitfalls of Inheritance," Steven Black explores common mistakes developers make when applying inheritance in object-oriented programming, emphasizing its static and inflexible nature. He advocates cautious use, stressing that subclasses should truly be specialized types of their parents and highlighting the need to separate interface from implementation. Black also warns against deep inheritance hierarchies, improper behavioral overrides, and overly visible members when extending classes. He recommends combining inheritance with composition for flexibility, proper method call-ups to preserve general behavior, and thoughtful interface design to create maintainable, robust systems.