| Developing A Vector Based C# Drawing Application - Part 3 |
| C#Today |
| In the first part of this series, Budi Kurniawan discussed the specification for a vector based C# drawing application. In Part 2, we looked at the Shape abstract class and the seven classes that inherit it. We also examined how an event handler works in a Windows application and we briefly discussed the System.Collections namespace. In this final part of the project, we will complete the development by discussing the DrawingArea custom control, the Color and Pen classes from the System.Drawing namespace, and object serialization - which is used to persist our drawing to a file, to be restored at a later stage. |
|
| Memory Game |
| C# Corner |
| This is a memory game where you can use your favorite pictures (.bmp, jpg, gif). Therefore you specify the directory/ies where the desired images are contained in the settings (Settings/Customize../Add). You can also make some other customizations like how many cards are displayed on the screen, or how the pictures are rendered (clip off an area to fit into the cards or stretch/shrink them). |
|
| Object Serialization in .NET |
| MSDN |
| Why would you want to use serialization? The two most important reasons are to persist the state of an object to a storage medium so an exact copy can be recreated at a later stage, and to send the object by value from one application domain to another. For example, serialization is used to save session state in ASP.NET and to copy objects to the clipboard in Windows Forms. It is also used by remoting to pass objects by value from one application domain to another. This article provides an overview of the serialization used in Microsoft .NET. |
|
| Persisting Application data using Hashtable and IsolatedStorage |
| The Code Project |
| This article demonstrates a custom class that can be used to store and retrieve application data in an easy and reliable manner. It uses an extended Hashtable to persist data into Isolated Storage. You can download a sample project which demonstrates the use of this simple, but very useful class. |
|
| Printing Invoices |
| C# Corner |
| The other day, I decided to cruise ZDNET to look for a simple shareware program to make invoices. I have to say, I couldn't find what I was looking for, so I turned to C# and .NET. This program can stand improvements but it will get you started in creating an invoice and printing it to the printer. You can customize the invoice by changing the bitmap supplied in the download to an invoice of your choice and then move the controls to fit into the proper locations on the Background bitmap. This invoice layout was scanned in from Intuit's, Quicken 99 and modified to add a few features. |
|
| Run-time Serialization |
| MSDN |
| In this three-part series of columns, I will explain how the .NET Framework exposes its serialization and deserialization services. For almost all data types, the default behavior of these services will be sufficient, meaning that it takes almost no work for you to make your own types serializable. However, there is a small minority of types for which the serialization service's default behavior will not be sufficient. Fortunately, the serialization services are very extensible, and I will explain in these three columns how to tap this extensibility to do some pretty powerful things when serializing or deserializing objects. |
|
| Serialization |
| C#Today |
| One of the most fundamental jobs for a piece of software is saving a document and loading it back up again. This process has become known as serialization, and .NET has strong support for this. In this article, Matthew Reynolds takes a look at how to save and load documents for a simple WinForms application. As part of the work, he introduces a reference implementation for properly handling the creating, saving and opening of documents as laid down by the Windows guidelines. |
|
