To create a Code39 barcode using C# or any .net language first go to and download the C# library and build it. Direct link for version 2 source (

Add the zxing.dll file as a reference to your project.

        using System.Drawing;
        Bitmap bmp = BarCode39("Message");

        public Bitmap BarCode39(string codeMessage)
   writer = new;

            int width = 180;
            int height = 120;
            matrix = writer.encode(codeMessage,, 
                width, height, null);

            Bitmap img = new Bitmap(width, height);
            Color Color = Color.FromArgb(0, 0, 0);

            for (int y = 0; y < matrix.Height; ++y)
                for (int x = 0; x < matrix.Width; ++x)
                    Color pixelColor = img.GetPixel(x, y);

                    //Find the colour of the dot
                    if (matrix.get_Renamed(x, y) == -1)
                        img.SetPixel(x, y, Color.White);
                        img.SetPixel(x, y, Color.Black);

            return img;



I recently spent some time optimizing some 8 year old .NET code. The program would convert files, do some cleanup of data, and insert the data into a sql 2005 database. The problem was that it could take anywhere from 10 to 20 hours. It also would randomly crash and someone would need to babysit the process.

A lot of people would probably jump in at this point and start coding. I first decided to take a look at how the process was running. The program would load the data from a shared network drive as needed and then insert into a database that was also on another networked computer.

The first step was to copy all the data to the local computer before running the process. Next was to insert into a database on the local machine. This reduced the time of the process about 50%. That was good. Now we were down to 5 hours instead of 10. Next another developer noticed that the databases were set to an initial size of 1 MB and to only grow at 1MB. We changed that to an initial size of 200 MB and a growth size of I believe 10%. The process was now down to 1 hour.

The next step was to find out why it was randomly crashing. This involved reviewing the code and reviewing the process with the data technician. We discovered that most of the options in the conversion program have never been used in 8 years. So I removed over 50% of the code and streamlined the user interface. I added exception handling. Instead of just crashing the program we would now log were the errors were occurring so we could investigate further.

With this done the conversion of data was for the most part down to a few button clicks as long as there were no errors to investigate. With all the redundant code removed the process was down to 20 minutes.

A good example of useless code was every file that was converted was loaded into multiple hidden datagrids and then reset to nothing.

I still thought I could speed this up. The next step I took was to clean and split the one multi thousand line class into multiple classes. This may sound easy but it did take some work. As it would turn out the original class used class level variables for almost every variable a function used. There were only a few variables declared in the functions that needed them. So I had to sort out what functions used what variables and how they all related to each other. When I was done I had three classes that used no class level variables. All variables were declared in functions. The few places that required more then one function access to a variable had the variable passed in as a function parameter.

Cleaning the code and splitting it into three classes of course did not bring any speed improvements, but it did make it much easier to understand. If a function was passed the same parameter value it would always return the same result. This made it very easy to make the data conversion part of the program multi threaded. To be exact I used asynchronous delegates and had four conversions running at a time.

The time to run the conversion was now 2 minutes. At this point I decided it was not worth taking the optimization any further.

I have been playing around some with xwt ( I am looking forward to it reaching a release status.

Xwt is a cross platform (Window, Linux, Mac) toolkit for c#. Write your application once and it is native on all platforms. Nice.

On windows it uses wpf, linux gtk, and mac cocoa.

This is something I have wanted to do and have been experimenting with. I have modified fyiReporting in my fork called My-FyiReporting to allow using the designer inside my own application.

My-fyiReporting is a .net report designer and viewer that is written in c#. The designer and viewer are programmed with c# and winforms. There is also a new gtk# viewer available for those that need a report viewer on Linux.

See for binary packages of My-FyiReporting. See for the project details and source code.

Open a Report

The simplest way to use the designer is to create an instance of the designer form and then load the report that you wish to use. If you do not have a report to open then just create an instance of the form and show it.

First add a reference to RdlDesigner.exe in your project. Then add the following code where you need to use a designer. It is as easy as that.

fyiReporting.RdlDesign.RdlDesigner designer = new fyiReporting.RdlDesign.RdlDesigner("myFyiChannel", false);

Where it is passing in myFyiChannel as a parameter is the IPC name that is being used in the designer. This must be unique or it will through an exception. You will need to handle this. I would suggest creating only one instance of the designer and show it when it is needed.

Create a new Report

If you want to create to prompt a user to create a new report you can do it like this.

DialogDatabase dlgDB = new fyiReporting.RdlDesign.DialogDatabase(this)
dlgDB.SetConnection("The Connection String", false, DialogDatabase.ConnectionType.SQLITE);
if (dlgDB.DialogResult == DialogResult.OK)
    string rdl = dlgDB.ResultReport;
    System.IO.File.WriteAllText("Path\to\new\report.rdl", dlgDB.ResultReport);

You can then open the new report using method described above.

See for more details about embedding the designer.

I have created a new fyiReporting viewer for Linux using Gtk#. It is currently very basic but will show a report. The code can be retrieved from in the RdlGtkViewer project. I have currently tested it with Ubuntu 11.10.

All issues and feature requests can be put through the projects github issues page.

It is simple to use. Add a reference to the RdlGtkViewer assembly in your project and then add the RdlGtkViewer widget to one of your forms.

Lets say I added a new instance called rdlgtkviewer1 to my project. I can load a report with parameters with the following line of code. Code:

    new Uri(@"/home/peter/Projects/My-FyiReporting/Examples/SqliteExamples/SimpleTest3WithParameters.rdl"),
    "TestParam1=Hello and Goodbye&TestParam2=Testing parameter 2");