Channels ▼
RSS

.NET

.NET Components For Image Management


David is the founder of Pro Shooters, which produces software for organizing and managing digital images, and a wildlife photographer who specializes in North American mammals and birds. He can be contacted at www.cardinalphoto.com.


At Pro Shooters (www.proshooters.com), our primary product is DigitalPro for Windows, an image-management system for digital photographers. We sell to serious photographers who have large image libraries and often need to process hundreds or even thousands of images at a time. As a result, we serve a niche market and can only afford a small programming team. That means we need to be more productive than the competition to stay ahead. So, instead of trying to do everything ourselves, we rely on tools such as third-party libraries in areas where we can find excellent tools that don't compromise on quality and features.

Licensing an imaging library was an obvious candidate for us. After all, image formats are mostly standardized and there is no sense reinventing the wheel. When we were developing in Visual Basic 6, we relied on a set of COM components, but when we moved to .NET, we really wanted to go with a solution that leveraged the .NET Framework. We looked at Microsoft's .NET native imaging classes, but they had limited support for metadata, color management, and many of the image formats we needed. Consequently, we went shopping for a toolkit that included .NET classes and visual controls that we could use to read, display, process, and write image files in a variety of formats. In addition, we have our own libraries for doing specialized processing of vendor-specific formats (such as raw files), so we knew whatever solution we licensed would need to be extensible.

By the time we were ready to evaluate imaging toolkits, we had a checklist of important criteria, including architecture, feature set, flexibility, performance, extensibility, and support responsiveness.

Architecture had become increasingly important to us. Since porting DigitalPro to .NET, we'd been hampered by third-party components that were either only available in COM versions or had (at best) thin .NET wrappers. While they would work, they were difficult to debug and limited in how we could use them. So we were looking for a native .NET toolkit for best results. Of course, we did realize that some of the low-level raster code would be unmanaged, but our hope was to have that be minimal and be transparently integrated into .NET libraries by the vendor.

As you might expect for a new platform, most .NET toolkits had fewer features than their more mature COM-based competitors. Still, we zeroed in on dotImage from Atalasoft (www.atalasoft.com). What we liked about dotImage was that Atalasoft had taken .NET seriously enough to move almost all of its functionality over to .NET, and the company was serious about addressing any shortcomings in the .NET managed code features set, rather than forcing licensees to knit together COM and .NET.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Video