AddFlow for .NET is a .NET Windows Forms Custom control.

It provides approximately the same flowcharting/diagramming features as the ActiveX version but also some new features (class derivation, OwnerDraw property, Anti-Aliasing, custom shapes), more flexibility and a simpler and more powerful object model.

It has been completely rewritten in C# to take advantage of the infrastructure provided by .NET. It is 100% Managed Code. Free AddFlow ActiveX to .NET conversion tool. Convert AddFlow ActiveX output files into a format that can be used by AddFlow for .NET. XtoNetFlow allows you to convert a file created with the SaveFile method of the AddFlow ActiveX control version 4.2 to a XML file that uses the format of XMLFlow, a DLL provided with AddFlow for .NET. In other words, it converts a diagram created with the ActiveX version of AddFlow to a diagram usable by the .NET version of AddFlow.

This tool comes with source code in VB. It is installed with AddFlow. In brief, AddFlow for .NET offers the following advantages: A small deployment assembly, suitable for use on the Internet. The size of the Lassalle.Flow.dll file is just 252 Kb. A light programming interface: we have always preferred the quality to the quantity and we refuse to provide an inflation of classes and properties. A full integration with the .NET environment. A great flexibility (class derivation, OwnerDraw, Tag properties, custom shapes). Runtime royalty free. General Features: Drawings can be made interactively or programmatically. Distinct shapes, styles, colors, font can be defined on a per item basis (for a node or a link) or as default properties for the control. Support of several collections allowing you to traverse the graph in many ways. Many properties allowing to customize the control (CanDrawNode, CanMoveNode, CanMultiLink, etc...) or an item (XSizeable, YSizeable, XMoveable, YMoveable, Selectable, Stretchable, etc...)


http://www.lassalle.com/products.htm
$499

All,
I haven't seen this version, but I used the previous version within MSAccess (albeit about 5 years ago now). It was very straightforward to use (as a programmer). I didn't have any issues with memory-leaks or anything, and the support (by Lasalle) was excellent and timely.
I would seriously recommend looking at this control.
Regards,
Kieron


____________________________
Build it better, faster, quicker, easier.. then fix it (non-offical MS mission statement)