Keen to see CodeSMART 2013 for VB6 in action? Well, you have reached the right place. We have prepared for you a few sections illustrating several CodeSMART 2013 for VB6 key features.
- All the features it adds to Visual Basic are accessible through the main menu and four toolbars it registers with the environment.
- CodeSMART tools are hosted or display their results within dedicated tool windows that can be moved or docked.
- Code view enhancements are displayed directly in the Visual Basic standard code editor window.
- Tabs are added to the Immediate window, which is thus converted into a central reporting place while it does not loose its initial functionality.
- Full screen support: yes, it's true, you can code in VB6 while completely maximizing the work area!
- Tabbed MDI IDE: CodeSMART can change the Visual Basic standard multiple document interface (MDI) into a modern Tabbed MDI one similar to VS.NET and other modern environments.
- Inject beauty into built-in VB6 core subsystems like the Object Browser and the Intellisense - the old, 16-color icons are gone and new, modern icons are now used, in line with CodeSMART's main subsystems.
- Branch Lines are drawn to emphasize control statement branches, that is lines drawn between the opening and closing parts of each control statement; very useful in visualizing code nesting.
- End-of-Line Details represent descriptive comments at the end of certain control statement closing parts; can be used to identify a long branch.
- Hotspots are visual markers for control statement and procedure main parts; can be used to navigate (with mouse clicks) between the opening and closing parts of the control statement/procedure, and to emphasize a certain branch line.
- Current Line Highlighting, as the name implies, assists the developer by highlighting the active code line with a grayed background.
- Physical: where components are displayed grouped in standard folders like in the built-in Project Explorer. Components can be further expanded to show their procedures, variables, event down to code flow items (select-case structures etc).
- Logical: where components can be logically grouped in user defined folders to ease the application's functional scheme comprehension. Code expansion is also available like in the above-described view.
- The history pane: tracks down the last visited items, that is: last opened Project Explorer items, double-clicked Immediate window pane results, edited code elements and viewed code items (if configured to do so). Persistent between sessions on a per-project basis.
- The node search pane: used to search for nodes in the CodeSMART Project Explorer.
- The workbench pane: this one can help you focus on certain elements by defining shortcuts to them. Persistent between sessions on a per-project basis.
- The Library Explorer can be used either as a dockable toolwindow, or docked with the CodeSMART Project Explorer.
- Both horizontal and vertical split view styles are available.
- Custom Code items (used by the Custom Code Inserter and Remover) and Multiple Copy and Paste Buffers are placed in special folders.
- Designer templates feature a real-life zoomable preview in a dedicated pane.
- Dead (unused) code and symbols: code that is no longer used. This code usually has a negative impact on the compiled program size, not to speak about having a significant negative role in code readability.
- Performance issues: certain statements and code that is usually considered a bad choice from an execution speed perspective.
- Potential problems: code that has a known potential for generating errors.
- Designer issues: refers to most common designer-related (form, user control, user document, property page etc) issues.
- Control issues: refers to control-related problems.
- Other (general) issues: refers to problems that could not be included in the above two but still apply to the application user interface.
- comments that appear in code
- string constants used in code
- designer control Caption and the Text properties
- The Strings Reviewer: this tool does somehow share part of its goals with the spelling checker. Its purpose is to help you produce a correct user interface as for the text it displays, but while the spelling checker focuses on individual words correctness, the Strings Review was designed to ease the phase of logical word combination (phrasing) analysis and correction.
- The Code Commenting Conformity Checker: many organizations employ code documentation standards - and it is recommended even for single developers to adhere to such one. Enforcing a code documentation standard can be done by requiring descriptive comments for modules and procedures, and also by requiring code commenting to be done inside routines as well.
- The CodeSMART Code Builders represent a set of tools that allow you to quickly create property procedures, sub or function procedures and even collections classes. Also, a very useful feature is the one that switches an assignment operator's parts - especially when writing database applications and having to initialize local fields from a lot of database fields at initialization, then reverse the operation at unloading. Moreover, CodeSMART can help to quickly format regular or SQL strings.
- The CodeSMART Multiple Copy-and-Paste Buffers: CodeSMART extends the standard Clipboard with persistent additional copy-and-paste buffers. These buffers can be filled with any piece of Visual Basic code and their contents can be pasted into any Visual Basic code window by using a simple shortcut key system.
- Tab Order Designer: configuring/reconfiguring tab order on a form or user control by managing each control's TabIndex property value can be a very tedious task. CodeSMART has a Tab Order Designer which can help you automate this process. You can either set the order manually by simply sorting a list, or you can even let the tool automatically establish the tab order (it does this in a standard right-to-left, top-to-bottom sequence).
- Hotkey Designer: this tool allows you to automatically manage hotkeys in your application user interface. The tool provides a hotkey generation mechanism along with the possibility to preserve (lock) some already defined hotkeys.
Change Name and Text Properties: When you design a form, besides modifying control positions and sizes, the most often updated properties are Name and (whichever applies, if one) Text or Caption.
Plus you may want at some time to rename a certain control based on its Caption/Text property, for example rename a label with the caption "Surname" to "lblSurname" - or vice versa
(that is, perform a property-to-property value generation).
The CodeSMART Change Name and Text Properties tool can ease manual property setting and automate property-to-property value generation.
- New Control Properties: In the process of creating new UI items, a developer usually ends up setting a subset of properties for certain controls over and over. CodeSMART can do for you this tedious task at control creation time or whenever a new designer component is added, by applying default values to their properties in conjunction with UI Standard Properties Manager settings.
- Reshape (indent) your code.
- Manage the amount of blank lines used to emphasize certain code elements. You can instruct CodeSMART to insert a specified amount of blank lines before and/or after specific Visual Basic keywords and also to limit the amount of total consecutive blank lines.
- Split code lines that exceed a certain length and also perform the reverse operation. Also, already split code lines can be compacted.
- Wrap method definition lines, API declarations and 'As' variable declarations across multiple lines in benefit of code readability.
- Header comments: descriptive header comments added to components and procedures. Can be added to the current component/procedure only or in bulk.
- Embrace-type comments (block comments) used to enclose a block of code between descriptive notes.
- Inline comments: other comments (usually single-line, but not necessarily so)
- The CodeSMART Error Handling Engine: Welcome to the most powerful VB6 error handling system ever! It is based on the concept of error handling scheme i.e. an error handling template designed for a specific component or procedure. This template completely describes the error handling configuration: header, footer, line numbers and other options that configure the automatic insertion/removal process. Schemes can be assigned to different types of Visual Basic components (Classes, Forms, Modules etc.) or to procedures (members) that match a certain pattern.
- The CodeSMART Tracing Subsystem: CodeSMART can help you automatically add or remove tracing instructions which can be extremely valuable in debugging tasks. This is achieved by adding a dedicated module to your project (source code included) and a reference to a special tool (AxVisualLogger) where the information can be logged (of course, you can use your custom logger if you want!).
- Finally, a small but handy feature for Handling Exceptions: Because Visual Basic doesn't offer built-in support for handling exceptions, you can use the MExceptionHandler module (provided by CodeSMART with full source code) which implements code for filtering any unhandled exceptions that may occur during a program's execution. This way your program can communicate unexpected events to a higher execution context that is eventually able to recover. Also, handling exceptions ensure that a termination code containing clean-up tasks is executed even if an exception or some other error occurs.
- Assigned tasks: tasks that are assigned to different members of a team, with start and due dates, code links, developer assignments.
- Personal tasks: similar to the assigned tasks, with the only difference that they are visible only to their creator and have no developer assignments.
- Comment (TODO) tasks: can be used as bookmarks in code, or as reminders etc.
- AutoSave and AutoBackup: pretty obvious what it does, and it works at specific time intervals.
- Mouse wheel support: you probably know that mouse wheel scrolling is generally not supported by the VB6 editor. Well, not anymore since CodeSMART adds that for you!
- Auto-checkout when trying to edit a file that is under source code control.
- Eventually enforce SCC action documenting.
- One-button close all windows (code or designer).
- Switch assignment values.
- Convert case (upper, lower, proper).
- Code Statistics: This feature can provide statistical information at a custom scope (component, project, project group).
- Custom Code Inserter: There are times during the coding process when you need to insert similar pieces of code in every procedure, function or property of a code module.
- Show File Differences: identify all the changes that were made to a file before saving it.
Download the latest CodeSMART 2013 for VB6 setup kit
You can use the button below in order to download a 30-day evaluation version of CodeSMART 2013 for VB6.
- If you are a CodeSMART 2013 for VB6 registered customer then you should download the product by using the full version private download URL that was disclosed to you at purchase time. If you do not have this private download URL any more then please click here to request it again. Please note that all requests are verified and only legitimate ones are honored - if necessary, you may be asked for additional purchase details.
Download an older version of 'CodeSMART for VB6'
- These product versions are now obsolete and have been superseded by CodeSMART 2013 for VB6.
- These setup kits are only available to registered users for the corresponding versions.
- FixPack setup kits are not available any more for these versions.
- What's new in Fix Pack 4
- 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 2013 for VB6
What's new in Fix Pack 4
January 22, 2014
- Fixed a crash that was occurring sometimes when End-of-line details were displayed only for statement blocks larger that a certain line count.
- Fixed "Error in loading DLL" that was reported when adding certain custom controls to a designer.
- The web update checker inaccurately detected a "new version" situation when the account VB6 was run on a non-administrative account (or without elevated credentials). Fixed.
- Fixed problems in toolbars which were caused by an older version of a custom toolbar control that was used by CodeSMART.
- Fixed a cryptic error that was reported after source code control check-out operations.
What's new in Fix Pack 3
December 10, 2013
- The "Extended Find" dialog height was incorrect on Windows Vista/7 and Windows XP systems while on single-line mode. Fixed.
- An error was reported at CodeSMART startup when checking the MSO.DLL version. Fixed.
- An 'Automation Error' happened sometimes when building the project/group. Fixed.
- Fixed some internal error handling idiosyncrasies
- Some icons were still low-color. Fixed
- The "About" pane in the CodeSMART Control Panel was incorrectly representing licensing state in some situations. Fixed.
- Added a simple web-update mechanism which will display a message when an update is available.
What's new in Fix Pack 2
October 29, 2013
- Sort Procedures was failing when encountering property procedures without a getter.
- The 'Register' button is not visible anymore on the 'About'/'License Details' pane if there is a full install.
- The "Office app is running" message box now has an explanatory notice on how to turn the check off.
- The Code Formatter did not insert blank lines after 'End Sub' / 'End Function' / 'End Property' statements even if configured to do so.
- An obscure "Method '~' of object '~' failed" error occurred on some systems when starting VB6 plus CodeSMART.
- An error was reported in certain conditions on SCC operations at project level.
- The Task List encountered problems on systems with certain time/date formats.
What's new in Fix Pack 1
September 23, 2013
- A glyph was drawn on some systems over public items' icon in the Project Explorer.
- A few users complained of slow editor updates, so a new setting was added in CVA "General" options: "aggressive refresh" (it controls how often the CVA gizmos are updated). Initially set to off, we recommend setting it to on if you have enough processing power (enough would mean here a physical machine with an average but modern CPU).
- If a node different than a component was double-clicked in the Project Explorer, the parent component node was not displayed in bold.
- Clear Immediate Window did not work in demo setup kits.
- If a copy of CodeSMART 2009 for VB6 evaluation previously expired on the machine, then CodeSMART 2013 for VB6 was already expired at install time.
- Links to registration were pointing to dead web pages.
- Settings from previous versions of CodeSMART were not carried over to the new version.
- The lyt layout files distributed by the setup kit were not up-to-date.
What's new in CodeSMART 2013 for VB6
September 16, 2013
Please find below a list with tools, improvements and features that are new in CodeSMART 2013 for VB6 (as related to CodeSMART 2009 for VB6).
- Hi-Color, modern icons in almost all subsystems.
- Visual refinements throughout the entire toolset.
- Hi-Color icons are injected by CodeSMART into the VB6 IDE built-in Object Browser and Intellisense subsystems.
- Code View Assistant branch lines are now colored, thus making multi-page branches more easily identifiable for example.
- Significant speed improvements for all bulk operations (i.e. insert/remove error handling code, line numbers, custom code, code formatter, sort procedures etc).
- Private components (only applies to relevant items, i.e. classes and user controls, and to project types that could actually export such items) are displayed with dimmed icons in the Project Explorer. This is supposed to replace the 'Bold public classes' option, albeit the old option is still there.
- Private code members are displayed with dimmed icons in the Project Explorer. This is supposed to replace the 'Bold public members' option, albeit the old option is still there.
- The currently selected component is displayed in bold in the Project Explorer. This works if the newer public components emphasizing method (i.e. private components de-emphasizing actually by using dimmed icons) is used only, that is if 'Bold public classes' is off.
- Windows 8 compatibility.
- Fixed extremely long delays at startup (i.e. if CodeSMART was set to load on startup) on systems where Microsoft Office 2010/2013 was installed, even if no Office app was running.
- In order to prevent startup delays altogether, CodeSMART now gives an explanatory notice if Microsoft Office 2010/2013 apps are running in the background (this check can be set to off in the CodeSMART Control Panel).
- Significantly reduced delays at startup when Microsoft Office 2010/2013 apps are running in background.
- When re-loading the addin (after unloading it in the same session), Code View Assistant features were not active on the currently active document.
- CsCmdLine was not working (the reg setting was for CS 2007, plus CreateProcessExA did not function on W7 and maybe Vista/8)
- CsCmdLine: Fixed an OpSwitch argument issue.
- If the task list admin password is the default one (which is the empty string) then no admin login prompt is displayed on regular operations. If you need security you will have to set a password first in the Control Panel (Task List / Password section).
- Spelling checker dictionary files do not require a separate download anymore.
- Better behavior on large fonts systems.
- Reviews result count is now displayed in the reviews combobox rather than in the Immediate window caption, thus having the entire project status visible when opening the combobox.
- A custom font size can be set for explorer toolwindows (Project Explorer, Designer Explorer etc) and Immediate window report lists (Find in Files, Find References, Code Analyzer etc).
- When editing, branch lines were deleted from the edited line. Also, branch lines were deleted from a line when a word on that line got selected.
- When switching to the Code Flow Explorer, if this one is empty and there is a valid selection (i.e. member in a code pane) then a parse is automatically invoked. Can be switched off in the Options dialog.
- When editing, branch lines were deleted from the edited line. Also, branch lines were deleted from a line when a word on that line got selected.
- The new position in Tab Order Designer is also marked by a red indicator line.
- Tab Order Designer now always pre-selects the control that is currently selected on the designer that is being invoked upon.
- The AutoText system now properly handles items starting with #. As a result, adding regions to code has is greatly simplified with the help of #reg and #ereg items (these will insert region start tag and region end tag respectively). Also, an AutoText item to help with bookmarks insertion was added (i.e. ‘bmk’).
- Added command for direct insertion of a comment header in the current member (Ctrl+') or component (Ctrl+Shift+'). Bulk operations are still available but only at menu level and with no keyboard shortcut.
- Ctrl+' was not trapped at all on some systems.
- When CSEHSkip was a member or component's modifier, the EH Inserter dialog did not initialize its "current scheme" and preview system correctly.
- All subsystems with code preview areas now use the same font as the code window; some will use a 1-point less font size if the editor font is too big.
- Setup program message boxes were not displayed on Windows 8.