Articles by Christopher G. Lasater (Articles: 26)

This article describes how to disable a ASP button on click to prevent multiple clicks and still fire the button event on the server.

This article will detail how you can use the OnPreRender event to redirect a page from inside a logical set of code without getting the 'Thread was being aborted' error.

One of those infamous ASP.NET server-side calendar controls that look and work like a JavaScript control! This is an easy plug-in for any project! I included some functions like being able to have the calendar display over other controls, and the ability to move through different months and keep the

This article gives a solution for cleaning up session variables that leap from one page to another in unexpected ways.

This article details a way to perform web security much like ASP 2.0 does it, using an ISAPI Filter.

This article describes how to set up and build a basic wsp solution file including handy installation scripts

I have included some scripts my co-worker Oleg Petrychenko gave me to install Sharepoint 2007 from scratch

This article describes one way to build a Sharepoint Feature project in Visual Studio that can be built and deployed using WSPBuilder, it also includes Sharepoint Server install scripts, and explicit instructions on how to build a basic feature in Sharepoint

This is a how to article about creating a List Definition feature.

This article provides a real world usage example for using delegates.

This is a quick helper to allow you to make the web reference URLs for your WSDL proxies easier to configure when switching environments.

Commands are useful tools when dealing with behaviors in objects. By making the request to an object, a Command object, and storing the command in an Invoker object, we can modify and keep historical records of different actions performed on an object.

This is a hands on article on how to refactor to design patterns, in specific for this article, factory and strategy design patterns.

This article details a real world example of how to use the mediator.

This article details a real world example of how to use a Chain of Responsibility pattern.

The adapter and bridge patterns offer us another way to make our code more flexible, and gives us another option for code design. Developers new to OO may have already found they have used a version of one of these patterns in their code before, or can find a myriad of uses immediately.

This article details a real world example of how to use facade patterns to help you deal with a modular code system, such as business layer algorithms, or any code which you wish to extract into its own assembly/namespace and allow only specific access from outside the assembly/namespace.

This article will deal with Property methodology of Adaptive Object Modeling. Property pattern methodology maintains that the attributes of a class should be held as a collection of properties, as opposed to single instance variables, which can be changed at runtime.

Adaptive Object Modeling is a relatively new concept in object oriented design that has found some roots in advanced development processes.

Strategy methodology maintains that the operations and business rules or code flow of a class should be held as a collection of properties, as opposed to single method calls, which can be changed at runtime.

This article will deal with Entity Relationships as they relate to the Adaptive Object Model pattern. We will discuss and use for this example Martin Fowler's Accountability pattern, which gives us relationship formation, cardinality between classes, and is the basis for workflow in the AOM pattern.

This article explains how client interfaces can be dealt with via the pattern. Also gives some very good reasons why an interpretive pattern methodology should be used over more static code, and attempts to explain how and why business development solutions can implement the pattern.

This article will deal with several topics dealing with implementing actual data into the AOM model.

Object Oriented Programming has been around for a long while, so I know there are a thousand articles, books and various writings on the subject. My goal in writing this one is just to clarify ONE MORE TIME some very basic aspects of OOP that I think are sometimes missed or overlooked.

This is a short article giving a breakdown of Microsoft's Domain Specific Language examples for software factories.

This article will deal with how to make the AOM pattern methodology useful in actual projects.