This page contains a brief presentation illustrating the main features CodeSMART 2009 for VS.NET adds to VS.NET 2002, VS.NET 2003, Visual Studio 2005 and Visual Studio 2008.

1. CodeSMART Integration with The Visual Studio 2008, 2005 And Older IDEs

1.1. General Integration Notes

CodeSMART is tightly integrated with Visual Studio - all its commands and tools are accessible through the main menu (1) and four toolbars (2) it adds to the environment. Other CodeSMART 2009 tools are hosted or display their results within special tool windows - for example, pictured below are (3) the CodeSMART 'Code Explorer' and (4) the CodeSMART 'Find and Replace' tool windows.

Back To Contents

2. Structured Navigation with The CodeSMART Explorer Tools

2.1. The Code Explorer

The CodeSMART Code Explorer is a code navigation and management tool that integrates features from both the standard Solution Explorer and the standard Class View. Its main design goal was to help the developer locate code as quickly as possible. For a solution and its projects it displays a single hierarchical view with files, folders, classes, methods etc.

The CodeSMART Code Explorer supports filtering, searching and view customization; moreover, it displays other useful code elements like regions, bookmarks, code flow nodes etc. XAML files are completely detailed in the Code Explorer window in two distinct node categories, one containing the specific XAML tag hierarchy and the other the code-behind file content. The XAML tag node appearance can be easily configured to show specific information like: the tag type, the Name and Content (or similar) attribute values, or other composite information. A complex set of commands is available for every element type displayed by the Code Explorer through the node associated context menu. The Navigation Helper Panes (History, Node Search and Workbench) were especially designed to help the user focus on a limited number of components and code elements.

• The History pane allows the user to keep in sight the last visited Code Explorer nodes or the last edited code elements (persistent between sessions).
  
• The Node Search pane allows you to quickly search (with partial search strings) for project item or code element nodes through the entire Code Explorer tree.
  
• The Workbench pane persists shortcuts to various elements (entire components, designer windows, code documents or code elements) on a per-project basis.
  

Back To Contents

2.2. The Code Flow Explorer

The Visual Studio code editor doesn't have tools to assist the developer in navigating inside a method body. When working with fairly simple methods browsing their code inside the code window is usually enough to grasp a general idea about the code logic, but trying to navigate complex methods with hundreds of code lines, nested conditional blocks and loops, can be a very tedious job.

The CodeSMART Code Flow Explorer can parse method code and output a tree representation thus offering instant access to the method's internal structure and logical code blocks.

Back To Contents

2.3. The Designer Explorer

With the CodeSMART Designer Explorer you can visualize a designer control hierarchy, select a control (which normally is not an easy job controls when controls overlap, are included in containers or simply are out of the visibility window) and benefit of several additional control-related operations and enhancements.

Back To Contents

2.4. Code Library Explorer

The CodeSMART Code Library Explorer represents a convenient way to quickly store and retrieve code pieces written in VB, C#, C++, HTML, XML etc, thus providing a valuable help in reusing, managing and sharing prewritten code. It can be seen as a code repository in which you can store and organize different code items, group them in logical folders and share them within a team.

Back To Contents

3. How To Locate Code with The CodeSMART Find Tools

3.1. Extended Find and Replace

The Extended Find and Replace subsystem adds powerful search and replace capabilities to the Visual Studio environment. It can perform code searches and replacements at any scope (member, document, project, solution) with a set of user-defined filters. The search target can consist of a single code line or of multiple lines and can contain wildcards or regular expressions. After the operation finishes, a comprehensive result list is displayed and matches are highlighted in code. Two Extended Find and Replace panes hold result lists for two different find/replace operations. Results found within strings and comments (if these were not configured to be skipped) are displayed by using specific colors. Additionally, a history combobox can be used to access previous find/replace operations.

Back To Contents

3.2. Find References

In the process of code writing as well as when analyzing prewritten code, knowing all the points where a certain code element is referenced can be extremely useful. There may be many purposes for such a task, like planning a refactoring, generally trying to understand a certain functionality, etc. The CodeSMART Find References tool can start from various code elements and output their list of references (works with both Visual Basic and C# projects).

Back To Contents

4. Refine Your VS.NET Projects with The CodeSMART Analyzer Tools

4.1. Code Analyzer

The CodeSMART Code Analyzer is a valuable tool that can be used to examine Visual Basic and C# code. It can be seen as a control quality tool for Visual Studio programmers who want to refine the code they write by making it smaller, faster and less error-prone. Code Analyzer features include detecting private dead code, code complexity issues, potential problems, optimization flaws and coding standards infringements.

Back To Contents

4.2. Designer Analyzer

The CodeSMART Designer Analyzer can be used to examine Windows Forms components for known problems. It can be seen both as a UI quality control tool and as a UI standards enforcement tool. Several options are available and grouped by problem categories. The analysis result set is listed in a comprehensive window.

Back To Contents

4.3. Spelling Checker

What can be more embarrassing than delivering an application and realizing you have spelling errors in its user interface? Let's face it, we all felt bad because of this at least once in our lives. We did it too - so we decided it's the time to have a Spelling Checker feature in CodeSMART.

Back To Contents

4.4. Strings Review

The Strings Review tool does somehow share part of its goals with the spelling checker. Its exact purpose is to offer a global and complete perspective on all the string constants used in code, but while the spelling checker focuses on individual words correctness, this new tool was designed to ease the phase of logical word combination (phrasing) analysis and correction.

Back To Contents

5. The CodeSMART Automated Text Entry (Or How To Write Code Blazingly Fast)

5.1. AutoText

Many times during the process of code writing you have probably used identical or similar code blocks, or written the same long code sequence over and over. In such cases, an auto-text feature like the one found in many professional text editors could have saved you a lot of time. Typing a few letters and then hitting a special keyboard combination is obviously much more productive than writing the same code piece again and again. This is what the CodeSMART AutoText system was built for; here's a sample of this system in action:

Back To Contents

5.2. SmartComplete

The CodeSMART SmartComplete brings an Intellisense-like list with specific language keywords, statements and global functions and user-defined items which are missing from the Visual Studio standard Intellisense list (in VS.NET 2002/2003 works for VB/C#/C++, while in Visual Studio 2005/2008 only works for VB).

Here are two examples on how SmartComplete works:

Example 1
		Private

Example 2
		WithEvents

Back To Contents

5.3. AutoBrackets

The CodeSMART AutoBrackets feature is a simple yet very useful tool that eases code writing by auto-completing the closing character in standard character pairs (parentheses, square brackets, braces and quotes).

Here's a sample:

Back To Contents

5.4. The Extended Clipboard

CodeSMART extends the standard Clipboard with 10 additional copy-and-paste persistent buffers. These buffers can be filled with any piece of text and their contents can be pasted into any Visual Studio code window by using an extremely simple shortcut key system.

Back To Contents

6. Tedious Coding Tasks Simplified By The CodeSMART Code Generating Tools

6.1. Simple Code Builders

These represent a set of wizards for creating basic code constructs like class definitions, methods, properties and indexers.

Back To Contents

6.2. Advanced Code Builders

Advanced Code Builders represent a set of tools which can be used to insert complex code constructs into Visual Basic and C# projects. By using these tools you can considerably reduce the time and effort that's usually necessary to write certain code like interface implementations, overridden methods, object construction and destruction, custom exception classes, custom formatter classes, collection classes, etc.

Back To Contents

6.3. Generate Exception Handling Code

Adopting an appropriate strategy for exception management can help you build successful and flexible applications that can be easily maintained and debugged. However, implementing a proper and consistent exception handling policy is not a trivial task - this is where the CodeSMART Exception Handling Tools come into play, as by using these tools you can:

• define your own exception handling templates enriched with CodeSMART standard parameters.
• designate a default template to be used for a specific programming language.
• share the same templates within a development team.
• explicitly mark different methods, properties and classes to use a specific exception handling template
• automatically insert and remove exception handling code at different levels (current selection, method, class, document, project, solution).

Back To Contents

7. Source Code Perfectly Formatted and Documented with The CodeSMART Code Maintenace Tools

As projects become more and more complex, adhering to certain standards usually becomes a necessity. These standards may include specifications and recommendations on how code should be formatted and documented. CodeSMART has dedicated tools that can help you meet such requirements.

Back To Contents

7.1. Code Formatter

The CodeSMART Code Formatter can be used to reshape Visual Basic and C# code based on certain standards. These standards can be specific to a single programmer or can be used for an entire programming team.

Back To Contents

7.2. Sort Procedures

Occasionally you may consider it necessary to rearrange code in a more logical and intelligible manner. The CodeSMART Sort Procedures tool comes to meet this requirement.

Back To Contents

7.3. XML Comments

XML documentation (XML comments), are a mix of XML and comments used to document code. CodeSMART not only extends support for XML comments to Visual Basic developers (VS.NET 2002/2003) but also offers an unified and flexible way to standardize this powerful feature in both Visual Basic and C# through the XML Comment Templates (avalable in all versions of Visual Studio).

Back To Contents

7.4. XML Comments Preview

The XML Comments Preview tool provides an easy way to vizualize pre-formatted XML comments when editing or browsing code.

Back To Contents

7.5. Regular Comments

Comments standardization is a must for every company, and adoption of such a standard by a single user is an extremely intelligent decision that will definitely show its benefits in time. Regular Comment Templates are intended to complement the XML Comment Templates feature described above; also, CodeSMART can ease commenting tasks by automating the regular comment skeleton insertion process.

Back To Contents

7.6. Code Commenting Analyzer

No matter if you write simple functions or complex classes, using relevant comments as often as possible is a requirement that every application developer should conform to. The CodeSMART Code Commenting Analyzer tool can help in getting a global perspective on code commenting at a certain scope by indicating in-method contiguous blocks of code that exceed a certain maximum length and have no comments, as well as code definitions that either have no comment defined or have an incorrect one from a standards point of view.

Back To Contents

8. Perfect Windows Forms UI Implementations with The CodeSMART Designer Tools

8.1. Tab Order Designer

Configuring/reconfiguring tab order on a Windows Forms designer by managing each control's TabIndex property value can be a very tedious task. The CodeSMART Tab Order Designer tool can help you automate this process - you can either set the order manually by simply sorting the control list or you can let the tool automatically establish the tab order.

Back To Contents

8.2. Hotkey Designer

The CodeSMART Hotkey Designer allows you to automatically manage hotkeys on a designer. The tool provides several hotkey generation methods along with the possibility to preserve (lock) some already defined hotkeys.

Back To Contents

8.3. Property Tips

The Property Tips lists a preset group of properties and their values in a special window that is displayed as a tooltip whenever the user pauses the mouse cursor over a designer control.

Back To Contents

8.4. Designer Assistant (only for VS.NET 2002/2003)

These tools are intended to ease working with controls while in designer mode. They offer a simple and quick way to identify a control, modify its size and position by using the keyboard in predefined fine or fast modes.

Back To Contents

9. And There Are Even More CodeSMART Tools...

9.1. AutoSave and AutoBackup (only for VS.NET 2002/2003)

CodeSMART offers the possibility to automate two mechanisms that can prove indispensable in application development: saving your work and creating backup copies.

Back To Contents

9.2. Code Statistics

The CodeSMART Code Statistics subsystem provides useful information about code at various scopes ranging from component up to the entire solution.

Back To Contents

9.3. Iterative Code

There are times during the coding process when the need to insert similar pieces of code in every method at a certain scope arise. For example, imagine your program generates a GPF. Probably having the possibility to trace code execution and see which is the last method that gets called before the GPF occurs could help. However, manually inserting tracing code into each method may take quite a long time. CodeSMART features an Iterative Code inserter/remover subsystem - by using it you will be able to insert and afterwards remove special code chunks at a certain scope in just a few seconds.

Back To Contents

Jump to:

• What's new in Fix Pack 3
• What's new in Fix Pack 2
• What's new in Fix Pack 1
• What's new in CodeSMART 2009 for VS.NET

What's new in Fix Pack 3 (October 20, 2009)

1. General: "Exception while cleaning the CodeSMART commandbars" at Visual Studio shutdown. Fixed.
2. General: "Disk or network error" at Visual Studio startup. Fixed.
3. General: "Exception while restoring CodeSMART commandbars visibility (Designer menu entries - Paste Alternate)" when closing the Visual Studio IDE. Fixed.
4. General: "Exception while initializing the main CodeSMART engine" when starting the add-in. Fixed.
5. General: "Exception while opening the personal database" when starting the add-in. Fixed.
6. Bookmarks: "Method '~' of object '~' failed" when creating a bookmark. Fixed.
7. Code Analyzer: "Exception while processing document" when running a code analyzer session. Fixed.
8. Code Explorer: "This item's control has been deleted" when adding a web service reference to an ASP.NET web application. Fixed.
9. Code Explorer: "Projectitem unavailable" when expanding a project in the Code Explorer tree. Fixed.
10. Code Library Explorer: "Exception caught by the generic procedure handler" when trying to start the Code Library Explorer. Fixed.
11. Code View Assistant: Member name highlighting failed in VB projects for code elements that had their name consisting of a reserved word in square brackets. Fixed.
12. Extended Find and Replace: "Object variable or With block variable not set" when stopping the debugger with the Extended Find and Replace results list non-empty. Fixed.
13. Extended Find and Replace: "Object variable or With block variable not set" when trying to execute a find operation. Fixed.
14. Outlining: "Method '~' of object '~' failed" was sometimes encountered when collapsing code. Fixed.
15. Spelling Checker: "Object variable or With block variable not set" happened under certain conditions when running a spelling checker operation. Fixed.
16. Web Update: UI fixes in the "New Version Available" dialog.

1. Code Builders: The implement common object operations and strongly typed collection code generators now use simpler names for parameters and variables.
2. Code Explorer: Added the option to display no namespace information in the type (class, interface) tree node text.

What's new in Fix Pack 2 (April 30, 2009)

1. General: The Commands Repair tool did not work if certain CodeSMART registry keys were not present, which was incorrect in most cases. Fixed.
2. General: Some corrections were made to the internal error reporting engine.
3. General: A database engine error was reported on CodeSMART startup on some systems. Fixed.
4. General: Spelling and phrasing corrections on several subsystems.
5. General: Current project language detection problem caused disabled language-specific (VB especially) settings on some dialogs. Fixed.
6. General: Systems configured to use 'large fonts' incorrectly displayed controls on the following windows: 'CodeSMART Control Panel', 'Extended Find and Replace', 'Designer Analyzer', 'Spelling Checker'. Fixed.
7. General: Initial centered position was incorrect for most windows on systems configured to use 'large fonts'. Fixed.
8. General: The 'Install On This User Account Tool' was not functioning. Fixed.
9. Code Explorer: Web site projects incorrectly displayed a 'References' folder. Fixed.
10. Code Formatter: Slight clarification in the Code Formatter dialog UI.
11. XML Comments: The Xml Comments Preview toolwindow did not display properly the current element's Xml Comment, nor did it use the correct style. Fixed.
12. XML Comments: The Customize Xml Comment Templates dialog preview style was inappropriate. Fixed.

1. Extended Find: The Extended Find now also works on HTML, XML, and XAML documents.
2. Extended Find: The replace feature now also works on HTML, XML, and text documents.

What's new in Fix Pack 1 (December 22, 2008)

1. AutoText: Several user interface problems were fixed.
2. Code Explorer: The 'Always show solution' setting was not read correctly from the system registry, leading to missing tree nodes in certain situations.
3. Code Explorer: Errors related to duplicate collection items were reported when scanning certain project item types.
4. Designer Explorer: Overflow errors were reported especially when using VS XAML designers.
5. Exception Handling: Changed the default state of the exception handling markers insertion to 'on because having it initially set to 'off' lead to the impossibility to undo an eventual initial test of the subsystem.
6. Extended Find: Find results were incorrectly displayed in green if they ended up in a code comment.
7. Extended Find: An error related to a disabled UI object was reported when initializing the search.
8. General: Solved a conflict with the AnkhSvn add-in.
9. General: Visual Studio settings were not correctly read from the system registry if a root suffix was used.
10. General: The Diagnostics tool did not work as expected in both editions of the product.
11. General: Several grammar errors which affected the VB parser were corrected.
12. General: The CodeSMART initialization progress dialog caused an error if another add-in or package (or VS itself) displayed a modal dialog at startup.
13. History: The user can now customize the color used to display history items that are not linked to locations in the current document.
14. Standards Manager: An error was reported at initialization due to inadequate null handling.
15. Standards Manager: The process of adding a user defined prefix/suffix for a certain type was flawed.
16. Try-Catch Templates Manager: The keyboard shortcuts system was incomplete and partially nonfunctional in VS2005 and VS2008.
17. Try-Catch Templates Manager: The Del key was unusable in the code editing pane in VS2002 and VS2003.
18. XML Comments: Handling of the XML tag closing character (the 'greater than' sign) in VS2005 and VS2008 ended up in duplicating the closing tags.

What's new in CodeSMART 2009 for VS.NET (August 20, 2008)

1. AutoText: The AutoText subsystem was revised in terms of efficiency and flexibility, and the auto-complete functionality was extended to XAML, SQL, ASP, HTML and JScript code.
2. Code Explorer: An option was added for alphabetically sorting children of aspx file nodes.
3. Code Explorer: Additional information is displayed on the Visual Studio status bar when expanding container nodes (projects, files, types, etc).
4. Code Explorer: CodeSMART now supports tree synchronization with XAML and JScript code.
5. Code Explorer: A stop-operation mechanism is now available when expanding the 'Derived Types' (the expand action triggers a derived types search).
6. Code Formatter: The column limit on which CodeSMART may split code lines was extended from 140 to 2000.
7. Code View Assistant, Name Highlighting: Property-style events (i.e. events with explicit implementation code) are now processed.
8. Designer Explorer: The Designer Explorer can now be instructed to display control type names using a 'short' form (the previously existing option applied to 'System.Windows.Forms' controls only).
9. History: Items that belong to the currently active document are now emphasized in the history pane.
10. History: The History list is now updated when double-clicking on a result item from one of the CodeSMART result lists (for instance: Find and Replace, Spelling Checker, Code Analyzer, etc).
11. History: The History list is now updated when viewing a code element for more than a certain (customizable) time span.
12. New Collection Class: The generated collection class code can now be additionally inserted into a separate class file.
13. New Property: The 'New Property' feature can now be used for generating auto-implemented properties (C# 3.0 specific).
14. Spelling Checker: XAML support was added to the Spelling Checker subsystem.
15. Statistics: XAML and JScript support was added to the Statistics subsystem.
16. Strings Review: XAML support was added to the Strings Review subsystem.

1. General: Fixed incorrect initial toolbar positions on the X-axis.
2. General: On VS2005 Standard edition, CodeSMART popped errors caused by certain COM interface issues.
3. General: Heavy optimizations on subsystems depending on keyboard processing (Name Highlighting, Code View Assistant, History, AutoText, Smart Complete etc).
4. General: Algorithm optimizations in several subsystems (Spelling Checker, Comments Analyzer, Strings Review and Statistics) led to correcting high GDI object consumption issues and to reducing the processing time dramatically.
5. General: The setup routine failed to correctly identify the Visual Studio version in some situations.
6. General: The main menu did not entirely fit on systems with resolutions of 1024x768 or 1280x800. Reduced the main menu height by reorganizing the analysis and review tools in a popup.
7. AutoText: Selecting a folder node in the AutoText Manager dialog did not disable the 'Parameters' toolbar popup; further attempting to use the popup entries lead to errors.
8. Code Analyzer: For and ForEach variable initializers were incorrectly reported as being 'dead code' if they were not explicitly used within the block structure body.
9. Code Explorer: Several reports indicated slowness when performing operations (expanding nodes, clicking nodes repeatedly, syncing with code, tree content refresh, etc) on tree structures for projects with many components.
10. Code Explorer: Solved 'Projectitem unavailable error conditions.
11. Code Explorer: CodeSMART failed to display the "unsupported project" node if the solution consisted of a single project and the solution node was configured (in Visual Studio 'Options') to be hidden.
12. Code Explorer: CodeSMART did not correctly display service references in the Code Explorer tree.
13. Code Explorer: Performing a source code control operation on an aspx file was not followed by refreshing the state images of the aspx child file nodes.
14. Code Explorer: After expanding a code element node, the tree incorrectly scrolled to the selected node (this usually led to having the expanded node moved out of the view).
15. Code Explorer: An error was reported sometimes when refreshing unusual Visual Studio project types (like BizTalk projects for instance).
16. Code Explorer: In certain situations, selecting several file nodes in the Code Explorer tree and trying to open them in bulk led to having only the first selected file opened.
17. Code Explorer: Clicking the 'Expand Project Nodes' toolbar button was reported to be ineffective for solutions with a single project when the solution node was configured (in Visual Studio 'Options') to be hidden.
18. Code Explorer: Significant optimizations were applied to basic node operations on file children nodes of types other than code element (i.e. code flow nodes, bookmark nodes, JScript and XAML nodes, etc).
19. Code Explorer: When using the 'Synchronize in Code Explorer' code window context menu entry the focus was given to the last used Code Explorer pane instead of the tree itself.
20. Code Explorer: An error was reported when expanding empty JScript file nodes.
21. Code Explorer: The XAML and JScript file content was not shown in Website projects.
22. Code Explorer: Multiple node selection was sometimes reported as a result of tree synchronization with code or when asking for a node synchronization from the History pane.
23. Code Explorer: When having a code element node selected and then clicking in the (already open) corresponding code window, the parent component node became selected.
24. Code Explorer: A new algorithm for establishing the code element image was implemented in order to fix delays on tree scanning.
25. Code Explorer: An error message followed sometimes by a general Visual Studio lockup occurred when double-clicking code element nodes in the Code Explorer tree, if those elements were part of an 'aspx' code behind file whose code window was previously closed.
26. Code Explorer: An error message was sometimes displayed when removing a project from the solution.
27. Code Explorer: In Visual Studio 2008, unavailable projects were mounted as 'unsupported' project nodes.
28. Code Flow: Several C# language constructs (like, for instance, the 'using' statement) were not displayed in the Code Flow window.
29. Code Flow: When double-clicking C# methods that had attributes, an incorrect code location was opened.
30. Code Flow: If two or more methods had identical bodies, parsing them in the Code Flow window yielded to only one method actually being parsed and to the other(s) being mounted as empty nodes.
31. Code View Assistant: Fixed a "An item with the same key has already been added" exception conditions.
32. Code View Assistant: The hotspot markers which go with end-of-line details remained visible on new Visual Studio sessions after this functionality was disabled.
33. Code View Assistant, Name Highlighting: Adding or updating a C# method parameter eventually led to not having the method name highlighted anymore.
34. Code View Assistant, Name Highlighting: When duplicating methods in C# and VB.NET code, the end-of-line details and name highlighting were displayed only for one of the duplicates. This persisted after the code had been corrected (i.e. the methods were given unique names).
35. Code View Assistant, Name Highlighting: Inserting a type with members in a C# document led to having this type's contained members not processed.
36. Command Assist: An untrapped exception sometimes caused the tool to exit prematurely.
37. Commenting Tools: Fixed an 'Object variable or With block variable not set' errors while loading the 'Regular Comment Templates' dialog.
38. Designer Analyzer: The Designer Analyzer feature displayed several error messages when analyzing a control that defined a property named 'Font' but not of the 'System.Drawing.Font' type nor deriving from it.
39. Designer Tools: No designer assistance (as in being supported by the Designer Explorer, Tab Order Designer, Hotkey Designer, etc) was available for designer classes that inherited from component objects other than the default ones found in the 'System.Windows.Forms' namespace.
40. Find and Replace: The 'search and replace' operation could not be executed on the current document scope if this corresponded to an opened solution item file.
41. Find and Replace: CodeSMART incorrectly detected and reported string matches found within comment blocks when the 'Skip Comments' option was enabled.
42. Find and Replace: Trying to skip search results found within comments by properly configuring the operation option set was reported to fail for C# and C++ block comments.
43. Find References: Existing Find References result markers were not updated in code on subsequent operations.
44. History: Performing certain CodeSMART operations that changed code in the active document (for instance: Code Formatter, Sort Procedures, Iterative Code, etc), was followed by an unnecessary history list update.
45. History: Certain history items were lost after setting options through the 'CodeSMART Control Panel'.
46. History, Node Search, Workbench: The navigation pane public items were incorrectly bolded if the corresponding Code Explorer option (which allows marking public nodes with bold text) was enabled.
47. Legacy Error Handling: The line numbering engine (for VB components, both the inserter and the remover) did not process property getter and setter members.
48. Name Highlighting: Incorrect name highlighting was applied to those C# properties whose type names started with the property name string.
49. Name Highlighting: Editing C++ code was reported to be extremely slow when the Member Name Highlighting feature was enabled.
50. New Class: In some situations an error occurred when trying to insert a new class into a C# aspx code behind file.
51. New Control Spy: When placing an ampersand character (&) in the text field it caused for the next letter in the control name field to be capitalized.
52. New Property, New Method: These code builders were revised in order to avoid several Code View Assistant repaint problems.
53. Result Panes: Several errors occurred when trying to save a CodeSMART pane results (like: Find and Replace, Code Analyzer, Designer Analyzer, etc) if overwriting a previously saved, read-only file.
54. Sort Procedures: An error message occurred sometimes when trying to sort aspx code behind files.
55. Spelling Checker: Spell-checking at the current method scope yielded to an error message being displayed when dumping results in the dedicated toolwindow pane.
56. Spelling Checker: Spelling Checker failed to correctly report and point in code misspelled words which were split on two consecutive lines.
57. Statistics: An error occurred rarely when running code statistics on large projects.
58. Try/Catch Blocks: When enclosing with the default try-catch block without using maker comments, if the header code did not end in a newline then the resulting code was erroneous.