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.
Source Insight™ is a project-oriented program editor and code browser, with built-in analysis for C/C++, C#, and Java programs. Source Insight parses your source code and maintains its own database of symbolic information dynamically while you work, and presents useful contextual information to you automatically.
Not only is Source Insight a great program editor, but it also can display reference trees, class inheritance diagrams, and call trees. Source Insight features the quickest navigation of source code and source information of any programming editor.
Source Insight features quick and innovative access to source code and source information. Unlike many other editor products, Source Insight parses your source code and gives you useful information and analysis right away, while you edit.