ComponentOne spells out changes

This article was originally published in VSJ, which is now part of Developer Fusion.
ComponentOne has released IntelliSpell, a spell-checker application for Visual Studio 2008 and 2005. It claims to be capable of checking 400,000 words per second, and is equipped with developer-friendly task lists and wiggly underlines to help speed documentation correction. A free Community Edition has been made available for eliminating mistakes in comments, XML documents, string constants, and HTML within files you are working on. A Professional edition provides the ability to spell-check your entire solution, and comes with 16 language dictionaries, and the ability for custom dictionary additions.

Also new is ComponentOne Studio Enterprise 2008, which includes Studio for ASP.NET, Studio for WinForms, Studio for Mobile and Studio for ActiveX, and is compatible with both VS 2008 and 2005. The biggest addition is Studio for WPF, which uses the WPF approach to design so that an entire component UI or specific UI parts can be customised in XAML without writing any code. The C1WPFChart control has a simplified and more flexible object model, driven by a single main chart component for both 2D and 3D plotting. C1WPFSchedule provides a number of predefined views for representing data in DataStorage, such as Day view or Month view. Each view is fully represented by a single style; each of them is fully defined in XAML.

The full list of components in Studio for WPF is to long to list here, but it includes everything you would expect and supports data binding, data visualisation within grids, scheduling, charts, reporting, and more.

You might also like...



Why not write for us? Or you could submit an event or a user group in your area. Alternatively just tell us what you think!

Our tools

We've got automatic conversion tools to convert C# to VB.NET, VB.NET to C#. Also you can compress javascript and compress css and generate sql connection strings.

“Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.” - Brian Kernighan