Infragistics WPF controls

.NET Design Patterns : The decorator pattern. Adding new behavior to your existing objects.

  .NET Design Patterns series: Part 1 The Decorator pattern   A brief introduction to software design patterns Hello and welcome to my first article in a series on design patterns.  A design pattern is simply a documented solution to a common software design problem.  This idea is extremely useful in the world of software development.  When designing and writing code, chances are whatever your task may be, someone has already accomplished what you've been tasked to do.  In fact, many developers have probably accomplished the task at hand.  Why reinvent the wheel?  There are many benefits to practicing and using design patterns. Industry standards Design patterns are deeply ingrained in the world of software development.  As such, you can look at tried and tested design patterns as "best practices".  If you practice and understand solutions that are accepted by the software development community, your software solutions will improve as a result. Efficient Communication Design patterns are defined and described using a unified set of terms.  As you practice design patterns, you will master these terms and in effect, you will be able to communicate much more effiecently with other developers.  You will spend less time trying to describe a potential design when you understand how to describe the concepts clearly by using a unified terminology.  As a result, other junior developers on your team will be more likely to try to learn design patterns which will make your overall team more efficient. Brief history of design patterns Kent Beck and Ward Cunningham began experimentation with design patterns in the context of computer science in the year 1987.  Most of the works on design patterns have been based on their works. Popular books on design patterns Design Patterns: Elements of Reusable Object-Oriented Software Patterns of Enterprise Application Architecture. Pattern-Oriented Software Architecture, Volume 1: A System of Patterns Pattern-Oriented Software Architecture, Volume 2: Patterns for Concurrent and Networked Objects Pattern #1: The Decorator pattern, Adding new behavior to existing objects I've decided to start this series with patterned called the Decorator pattern.  I suppose it's best to start with the formal definition of the pattern. The Decorator Pattern attaches additional responsibilities to an object dynamically.  Decorators provide a flexible alternative to subclass for extending functionality. Too much inheritance can be a bad thing  Inheritance is an important part of object oriented design.  However, just like anything else, too much subclassing can be a bad thing.  The idea behind a great object oriented application is to design your objects with change and reuse in mind.  If you find yourself creating 20+ subclasses of an abstract class, you may want to step back and look at your design.  With each new subclass that you design, there's a another class that you must maintain and change.  Remember, to always design your classes to be Open for extension, closed for modification.  This makes for easier maintienence and flexible designs. The Decorator pattern allows you to add behavior to existing classes at run time through object composition.  This means we create a class to "decorate" another class with new functionality.  The class to be decorated would be passed into the decorator object's constructor and the reference would be stored as a field.  This process can be repeated to achieve new functionality when calling the common contract of the class to be decorated. The article example Imagine the idea of an article.  There are many different types of articles.  There are news paper articles, blog articles, code project articles, magazine articles.  The list goes on and on.  In the age of electronic articles, it would be handy to write an article class and provide a post method.  The post method would contain any external site API calls required to publish the article to it's destination.  When posting an article, you may want to accomplish other tasks at the same time, such as advertise the article.  Perhaps you'd like to advertise your new article via Twitter.   OOP Principals: Open for extension and closed for modification You could add the code to tweet your new article right into your the article base class, however, this would go against our Object Oriented design princiapl "Open for extension, closed for modification".  Wouldn't it be better to add this new behavior to our articles at run time?  The decorator pattern allows us to do just that!   Examine the following class diagram.  And here is the code.. Article.cs   using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Threading.Tasks; namespace DecoratorPatternApplication { /// <summary> /// Defines the methods and properties required for an article to be posted on the web. /// </summary> public abstract class Article { #region "properties" public string Title { get; set; } public string Url { get; set; } public string Body { get; set; } public string Author { get; set; } #endregion #region "methods" /// <summary> /// Provides a method to "Post" the article to it's destination. /// </summary> public abstract void Post(); #endregion } } Decorator.cs using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Threading.Tasks; namespace DecoratorPatternApplication { /// <summary> /// This interface takes an /// </summary> public abstract class Decorator : Article { //Holds a reference to the componoent to be decorated //in this case an article. protected Article _article; /// <summary> /// A emthod to provide the article to be extended. /// </summary> /// <param name="article">The article in which to add new behavior</param> public void SetArticle(Article article) { _article = article; } /// <summary> /// Implementation of the base classes' post method which calls the /// referenced article's post method as well. /// </summary> public override void Post() { if (_article != null) { _article.Post(); } } } } CodeProjectArticle.cs using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Threading.Tasks; namespace DecoratorPatternApplication { /// <summary> /// Represents an article to be posed to /// </summary> public class CodeProjectArticle : Article { public CodeProjectArticle() { } /// <summary> /// This would normally contain any calls to post the article to the automatically /// </summary> public override void Post() { Console.WriteLine("Posting the article {0} to {1}", this.Title, this.Url); Console.WriteLine(); } } } Tweetable.cs using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Threading.Tasks; namespace DecoratorPatternApplication { /// <summary> /// This interface takes an /// </summary> public class Tweetable : Decorator { //Holds a reference to the componoent to be decorated //in this case an article. protected Article _article; public Tweetable(){ } /// <summary> /// A emthod to provide the article to be extended. /// </summary> /// <param name="article">The article in which to add new behavior</param> public Tweetable(Article article) { _article = article; } /// <summary> /// Implementation of the base classes' post method which calls the /// referenced article's post method as well. /// </summary> public override void Post() { base.Post(); if (_article != null) { _article.Post(); } TweetArticle(); } public void TweetArticle() { if (_article != null) { Console.WriteLine("Tweeting about your recent article posting entitled {0}", _article.Title); Console.WriteLine(); } } } } BlogPost.cs using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Threading.Tasks; namespace DecoratorPatternApplication { public class BlogPost : Tweetable { protected Article _article; public BlogPost() { } public BlogPost(Article article) { _article = article; } public override void Post() { base.Post(); Console.WriteLine("Posting a personal blog called {0} to my personal blog site {1}.", this.Title, this.Url); Console.WriteLine(); } } } Program.cs using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Threading.Tasks; namespace DecoratorPatternApplication { public class Program { public static void Main(string[] args) { //Create an instance of our code project article CodeProjectArticle codeProjectArticle = new CodeProjectArticle { Title = "Code Project Article: Why learn Assembly language?", Author = "Buddy James", Body = "All of the article's body would go here.", Url = "" }; codeProjectArticle.Post(); BlogPost personalBlogPost = new BlogPost { Title = "The Decorator pattern. How to extend the behavior of your existing objects", Author = "Buddy James", Body = "All of the article's contents would go here.", Url = "" }; //Lets post a tweet when we post our blog article Tweetable TweetBlogPost = new Tweetable(personalBlogPost); TweetBlogPost.Post(); Console.ReadLine(); } } } I've attached the entire solution so that you can see how it works.  You can download the solution Here (78.94 kb)   Notice that the post and tweet methods contain calls to Console.WriteLine().  Obviously in a real scenario these methods would contain calls to actually "post" or "publish" the  article. I hope you've enjoyed my first of many articles on design patterns. Thanks and keep reading! ~/Buddy James kick it on  

WPF Validation tutorial for the rest of us. Learn to use IDataErrorInfo to automatically validate your views.

    WPF Validation for mere mortals I've recently jumped on the WPF bandwagon and I've fallen in love with this technology.  XAML is a fascinating animal indeed.  The declarative nature of the language leaves much to be explored.  There are many ways to solve the same problem.  On my quest for knowledge, I've been researching the intrinsic validation functionality of WPF.  Unfortunately, most every example I've ran across on blog posts and have been a bit too complex for my blood.  I find often that you need learn other subjects before you can begin to understand how the validation works.  Don't get me wrong, the examples are really nice.  However, when I'm learning something, I want a straight to the point example of the topic at hand.  It's with this idea in mind that I bring you a simple tutorial on WPF validation. I will be illustrating this example using the MVVM (Model-View-ViewModel) Pattern.   Click here to download the entire source (74.08 kb)  Consider the following code  The view MainWindow.xaml <Window x:Class="ExceptionValidation.MainWindow" xmlns="" xmlns:x="" xmlns:viewModel="clr-namespace:ExceptionValidation" Title="MainWindow" Height="350" Width="525" > <Window.Resources> <viewModel:MainWindowViewModel x:Key="mainViewModel"/> </Window.Resources> <StackPanel DataContext="{Binding Source={StaticResource mainViewModel }}"> <TextBlock>Enter total amount</TextBlock> <TextBox Width="200" Name="txtTotalAmount" > <Binding Path="[0].TotalAmount" ValidatesOnDataErrors="True"> <Binding.ValidationRules> <ExceptionValidationRule></ExceptionValidationRule> </Binding.ValidationRules> </Binding> </TextBox> <Button Content="Button" Height="28" Name="button1" Width="84" /> </StackPanel> </Window>     The viewmodel MainWindowViewModel.cs using System; using System.Collections.Generic; using System.Collections.ObjectModel; using System.Linq; using System.Text; using System.ComponentModel; namespace ExceptionValidation { class MainWindowViewModel : ObservableCollection<Product> { public MainWindowViewModel() { Add(new Product { TotalAmount = 3 }); } } }   The model Product.cs using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.ComponentModel; namespace ExceptionValidation { public class Product : INotifyPropertyChanged , IDataErrorInfo { public event PropertyChangedEventHandler PropertyChanged; private int _totalAmount = 5; public int TotalAmount { get { return _totalAmount; } set { _totalAmount = value; OnPropertyChanged("TotalAmount"); } } public void OnPropertyChanged(string info) { PropertyChangedEventHandler handler = PropertyChanged; if (PropertyChanged != null) { handler(this, new PropertyChangedEventArgs(info)); } } public string Error { get { throw new NotImplementedException(); } } public string this[string columnName] { get { if (columnName == "TotalAmount") { bool valid = true; if (_totalAmount > 10) { valid = false; } if (!valid) { return "The total amount cannot exceed 10!"; } } return null; } } } } A brief introduction to MVVM  As you can see, we have a XAML view, a viewmodel class, and a model.  The Model is a representation of an object's data.  In this instance, we are modeling a Product.  The viewmodel is an object that handles the change notification between properties in the model and elements on the view.  XAML properties, events, and bindings have the ability to tunnel (down the tree) as well as bubble (up the tree).   Binding the ViewModel to the view. In order to bind the ViewModel to the view, we must make it accessible to the view via XAML.  To accomplish this, we first have to import the namespace in which the viewmodel exists.  Examine the following code. xmlns:viewModel="clr-namespace:ExceptionValidation" Here is the equivalent in c# using ExceptionValidation; Once we've imported the namespace for use, we then need to define our MainWindowViewModel as a Resource of the current window. <Window.Resources> <viewModel:MainWindowViewModel x:Key="mainViewModel"/> </Window.Resources> This allows us to declare an instance of the MainWindowViewModel class by using the associated Key "mainViewModel". Binding the ViewModel As stated before the ViewModel acts as a "go between" for the View and the Model.  In order for the view model to communicate with our XAML view, we will bind the ViewModel to the StackPanel's DataContext. <StackPanel DataContext="{Binding Source={StaticResource mainViewModel }}"> XAML's ability to tunnel properties down from parent to child will allow each element inside the stack panel to make use of the DataContext binding that we've just setup using the Window resource's key mainViewModel. ObservableCollection<T> The viewmodel inherits from ObservableCollection<Product>.  The ObservableCollection<T> generic class represents a collection that can be utilized by WPF databinding.  This is possible because the ObservableCollection<T> class raises an event when items are added and removed from the collection. INotifyPropertyChanged The model implements the INotifyPropertyChanged interface.  This interface provides an event in which to fire any time a model property is changed.  This event notifies the bound element in the view that the property has changed. public event PropertyChangedEventHandler PropertyChanged;   public void OnPropertyChanged(string info) { PropertyChangedEventHandler handler = PropertyChanged; if (PropertyChanged != null) { handler(this, new PropertyChangedEventArgs(info)); } }   IDataErrorInfo The magic behind WPF validation comes from the implementation of the IDataErrrorInfo interface.  The interface implements the following members.  The this[columnName] indexer implements the logic of the validation rule. //Not used by WPF public string Error { get { throw new NotImplementedException(); } } public string this[string columnName] { get { if (columnName == "TotalAmount") { bool valid = true; if (_totalAmount > 10) { valid = false; } if (!valid) { return "The total amount cannot exceed 10!"; } } return null; } } The following XAML code binds the TotalAmount property of the first Product in the viewmodel's internal collection to the Text property of the TextBox element.  The ValidatesOnDataErrors attribute tells the textbox binding to raise an event when there is a valadation error.  When the event is raised, the bound element's template is changed to a new visual style that places a Red rectangle around the border of the TextBox.  When the error is corrected, the original template is restored.  Binding.ValidatesOnDataErrors <TextBox Width="200" Name="txtTotalAmount" > <Binding Path="[0].TotalAmount" ValidatesOnDataErrors="True"> </Binding> </TextBox> In the provided example, if you enter a value greater than 10 into the text box and tab out of the textbox, you will see that an error is raised causing the red outline around the textbox.  If you correct the error by replacing the value with a number less than 10, the red outline will disappear. This concludes my tutorial on WPF validation.  This is the very basic of validation methods.  There are many other advanced tutorials on the subject.  My next tutorial will involve utilizing custom validation attributes from the System.ComponentModel namespace to handle WPF view validation. Thanks for reading! ~/Buddy James kick it on  

Learning ILAsm, the backbone of .NET

Who cares about ILAsm or x86 assembly language anyway? I'm sure a lot of you are wondering why anyone would care about learning ILAsm.  It's not like you ever see it unless you disassemble an application.  ILasm or MSIL is the human readable translation of Microsoft .NET intermediate language.  ILAsm is a lot like classic assembly language.  It is a low level programming language that allows you to write programs one instruction at a time with a very minimal syntax.  I've explained the benefits of learning assembly language in my previous post, Why Learn Assembly Language.  In a nutshell, if you learn .NET at the low level of IL, you will have an understanding of what makes any .NET language tick.  You will have the knowledge to disassemble any .NET binary and debug your software at the instruction level.   This post is my first tutorial on writing code in ILAsm.  I hope you'll join me and become proficient in this language of kings.  You will have an edge over the competition and it will change the way you look at high level coding.  Enough talking, let us code! How to compile ILasm If you are a .NET developer, you most likely have an ILasm compiler on your computer which by the way is appropriately named ILasm.exe.  Simply launch the Visual Studio Command Prompt, navigate to the folder that you create your IL files and issue the following command. ilasm.exe is fine if you like to write code in notepad and drop out to a command prompt to write your code.  I myself prefer an IDE.  Visual Studio is an amazing IDE but for some reason the people over at Microsoft didn't see it fit to add support for ILasm into the product.  Never fear!  There is a free, open source alternative that is nearly identical to Visual Studio and it allows you to create and compile IL projects with syntax highlighting that works on Linux, Windows, and Mac OSX!  What is this application you ask? MonoDevelop   "Hello... World?" I know, I know, it's a tired, worn out cliche but far be it from me to interrupt the order of the programming gods and illustrate a programming language without starting with the infamous "Hello World!" example. //import the mscorlib assembly to give us access to Console and other basic classes .assembly extern mscorlib{} //define our assembly .assembly HelloAssembly { //define the version of this assembly .ver 1:0:0:0 } //define the executable module .module helloworld.exe //defin our main method .method static void main() cil managed { //set up the stack. In ILAsm, all values are placed on the stack and then manipulated. //here we will allocate memory for one value to be on the stack at a given time .maxstack 1 //define the main entry point to the application .entrypoint //load the emphamis phrase on the stack ldstr "Hello ILAsm!" //print the string from the stack to the console call void [mscorlib]System.Console::WriteLine(string) //return to end the program ret } If you have never seen asm or ILasm, I can imagine how strange this code snippet may look.  As I've stated before, ILasm is a very cryptic, low level language.  Let's breakdown the application. We start by importing the mscorlib library which contains much of the base .NET classes.  As the comments state, this library gives us access to the System.Console object.   Next, we define the assembly for our program.  All .NET executables are called assemblies.  Here we name our assembly as well as set a version number.  After we define our assembly, we define the executable module.  This is required in any ILasm application.   Now it's time to define our main method that performs the loading and printing of the string.  We start by defining the maxstack, that is, the maximum number of values that can be held in memory at a given time.  In ILAsm, you push values on the stack, perform operations on the values or use them as parameters to methods.  Since we have a maxstack of one, that means we can have only one piece of data to work with at any given time.  We use ldstr to load a string onto the stack.  If we were to load another string on the stack directly after the first ldstr call, the application will simply push the first value out of memory and the new string will be available to access. Finally, we call the WriteLine method on the System.Console object and we tell it to use the current string on the stack as it's input source.   So now you can load a string onto the stack and display it.  It's pretty interesting, although very limited as well.  How about we work with more than one value?  Let's try adding two numbers! Sum it up //reference to mscorlib .assembly extern mscorlib {} //define our assembly .assembly MiniCalculator { //the assembly version number .ver 1:0:0:0 } //create the required module .module MiniCalculator.exe //define our main method .method static void main() cil managed { //we plan to work with two integers this time .maxstack 2 //the main entry point to our application .entrypoint //load a string of instructions on the stack ldstr "OK. Class is in session. Who can tell the class what is the sum of 2 + 2? That's right, the answer is " //display the instructions to the user call void [mscorlib]System.Console::Write (string) //put the number 2 on the stack. Currently the previously loaded string, and the //number 2 are both on the stack. ldc.i4 2 //when we move another integer to the stack, this pushes the string off //now we have two instances of the number 2 on the stack ldc.i4 2 //add will add the two numbers on the stack and store the result add //lets tell the computer to look for an int on the stack and print it to the console call void [mscorlib]System.Console::Write (int32) //return to exit the application ret } We start the application as before by importing mscorlib, defining our assembly and module, and creating the method to perform our work.  We then load a string on the stack and use Console's WriteLine method to display the string.  We then load two integers onto the stack, pushing the string off of the stack.  We call add whichs adds the two integers and stores the result on the stack.  We use Console's WriteLine once again to display the answer. This concludes part one of my ILasm tutorial series. Please check back soon for my next installment in which we will tackle data types, loops, and classes! Until next time.. ~/Buddy James kick it on  

How to configure mono 2.10, .NET 4.0 and ASP.NET MVC to run on an Ubuntu Apache web server.

The challenge... As per my previous post [post title here], I wanted to configure mono on my recently installed Ubuntu machine.  Specifically, I wanted to be able to use the latest .NET functionality as well as ASP.NET MVC integration with Apache.  In this post, I plan to provide the steps and resources in which I took to accomplish my goals. Let's start with the Ubuntu machine.... The Ubuntu desktop specifications The machine in which I've installed Ubuntu is an OLD machine that I had laying around the house.  My Android has more horsepower than this old Dell, however, Ubuntu 10.4 seems to operate at a perfectly acceptable capacity.  I plan to "refresh" my Linux skills and look for spare RAM to add to this machine before I upgrade to Ubuntu 12.04.  The recommended minimum requirements for Ubuntu 12.04 are as follows; [For installing] The minimum memory requirement for Ubuntu 12.04 is 384 MB of memory for Ubuntu Desktop. Note that some of your system's memory may be unavailable due to being used by the graphics card. If your computer has only the minimum amount of memory, the installation process will take longer than normal; however, it will complete successfully, and the system will perform adequately once installed. [For upgrading] While the minimum memory requirement for 32bit is 384 MB, a minimum of 512 MB is needed for the 64bit installation. On systems with only the bare minimum amount of memory, it is also strongly recommended to use the "Install Ubuntu" option as it uses less memory than the full live session. Ubuntu Desktop System Requirements for 12.04 LTS What's with all the aPtitude? As much as I love aptitude, I'm quite annoyed by the time it takes for source repositories to list packages as "stable".  I understand that this has nothing to do with the package manager itself and that the Ubuntu version carries more of the blame, even so, I wanted to simply apt-get install mono-complete, I would be stuck with mono 2.4.  Since I wanted to use   some newer functionality, I had some planning to do.  The overall process went a little something like this; Find a bash script that compiles all of the mono packages that I needed to get the job done. Execute the script and watch some T.V while I waited for the massive compile to complete. Move the Apache mono module configuration into the "available modules" folder to enable mod-mono under Apache. I needed to create an Apache virtual host configuration file with the mod-mono specific settings that are required. I had to prepare my file system to serve my ASP.NET applications (c:\inetpub\wwwroot\ for all you Windows natives). I needed to provide a simple solution to publish ASP.NET applications from Visual Studio on my Windows 7 machine to my Ubuntu web server. Finally I needed to restart apache2, publish a web application and test the fruits of my labor. BASHing mono into shape As I stated before, I wasn't going to apt-get install my way into the wonderful world of mono with all of the specific details that my target installation required.  Luckily, I found this post  in which someone created a BASH script that would download all of the specific packages and compile the sources to produce the exact environment that I was after.  I'm sure  if I had used a modern PC it wouldn't have taken so long, never the less, the compilation was quite a time consuming task indeed!  The script was authored very well in that if there was an error detected, the script would break execution to make it easier for you to find what went wrong.  Fortunately, my compilation completed without a hitch!   Enabling mod_mono in Apache The BASH script had installed created the mod_mono.conf configuration file but I had to find it and copy it to the enabled modules directory so that Apache would recognize it. Here is the command that I executed from a terminal to copy the file to the proper location sudo cp mod_mono.conf /etc/apache2/mods-enabled Of course I had to find the configuration file before I could copy it sudo find -name mod_mono.conf With the configuration file in place, I restarted Apache to make sure all was well sudo service apache2 restart The service restarted successfully so I felt OK with what had been done so far. Creating the mono virtual host configuration file There is a webiste that will require you to fill in some input fields and click a button to generate this file the virtual host configuration with mono specific settings.  I merely had to modify one line of the file. The website is I simply used localhost as my server name and it generated the physical path of /srv/www/localhost. I used nano to edit the file and I modified the MonoDirectory line to point to the correct path of my mono_server4 binary's path which I was able to search and find to be /opt/mono-2.10/bin . Creating wwwroot, or /svr/www ... It was now time to prepare my file system to setup a home for my site hosting.  This basically involved creating some folders, setting permissions and creating an alias link or two. Create the directories sudo mkdir /srv/www sudo mkdir /srv/www/localhost Assign a root group to the folder sudo chown root:www-data /srv/www/localhost -R Change the directory attributes sudo chmod 775 /srv/www/localhost -R I then moved the virtual host site generated file to the appropriate path mv ~/Desktop/localhost.conf /etc/apache2/sites-available I then created a symbol link so I could refer to the vhost configuration file with leading zeros (Apache loads the configurations alphabetically). sudo ln -s ../sites-available/localhost.conf "000-localhost.conf" I restarted Apache, fired up firefox, browsed http://localhost and that's all it took...  I hope you enjoyed reading this article and I hope this helps someone configure ASP.NET MVC under Apache on Ubuntu using mono.  Until next time.. ~/Buddy James   kick it on  

About the author

My name is Buddy James.  I'm a Microsoft Certified Solutions Developer from the Nashville, TN area.  I'm a Software Engineer, an author, a blogger (, a mentor, a thought leader, a technologist, a data scientist, and a husband.  I enjoy working with design patterns, data mining, c#, WPF, Silverlight, WinRT, XAML, ASP.NET, python, CouchDB, RavenDB, Hadoop, Android(MonoDroid), iOS (MonoTouch), and Machine Learning. I love technology and I love to develop software, collect data, analyze the data, and learn from the data.  When I'm not coding,  I'm determined to make a difference in the world by using data and machine learning techniques. (follow me at @budbjames).  

Related links

Month List