Version

Date

Description

• Add-In registration changed to XML method.
  

• Add logging of opening .resx files during scan.
  

• Bug fix inferring ASP properties from resources.
  

• Fix logic to trap prohibited changes to project database in unlicensed version.
  

• Fix resource export for properties of child controls, such as menu items.
  (An old project database may contain duplicate records with different names for the same property, e.g. MainMenu.Item(0).Text and FileMenu.Text, but with the same resource name. This could result in the resource not being exported!)
  

• Improved proxy support for Microsoft Translator.
  
• Improved logging of detected files and of opening designer windows.
  

• Proxy address option to the setup dialog.
  (Not yet tested on a system which needs it!)
  

• Set GeneralIDs.ResourceName to NULL on adding a new string ID, to meet constraint if the project database is an access database.
  
• Disallow changing the status of a translation to online translation or imported localization in an unlicensed version.
  

• Reworking of the limitations in the unlicensed version.
  
• Minor changes to the templates MlString.vb and MlString.cs, to handle the case where there is no RootNamespace.
  
• Additional Import statements added to the template SelectLanguage.vb.
  

• Optionally indicate the translation status with the background colour:
  
  • white = edited in grid
    
  • blue = original text
    
  • yellow = from global database
    
  • green = from excel import
    
  • red = online translation (Microsoft Translator)
    
• Commands to change the translation status:
  
  • In the context menu
    
  • In edit mode, ALT-UP and ALT-DOWN move to the cell above or below, and change the status of the translation to edited.
    
• Optionally set the background colour in the Excel export in the same manner
  
• Extended support for Microsoft Translator:
  
  • New command in tools menu
    
  • New command in context menu (in language submenu)
    
  • New option in Add Language dialog
    
• Note: The background colour is important in conjunction with online translation, because we can't expect online translations to be of a high quality. In general, a translator will still have to check every single text.
  

• Uninstall removes registry entries which are created by the installation.
  Registry entries created by the Add-In itself are not removed (yet).
  
• Uninstall removes registry keys which are created by the installation, if they are empty.
  
• Error report via email contains the windows version.
  
• Translation status is shown in the context menu, and can be modified.
  

• Bug fix in translation memory dialog (incorrect field length in ADO.NET DataTable definition).
  
• New fields in project database (in preparation for new features) to:
  
  • identify StringIDs which have been explicitly added by the user
    
  • define a status for each translation.
    

• Bug fix in copy operation after selecting Apply to all in the multiple-usage dialog.
  

• The Add-In no longer updates the neutral .resx files for Forms, UserControls or Web pages. It is better to leave this to Visual Studio
  (Exception: If you edit the original text in the Add-In's controls grid, then the neutral .resx file will be updated.)
  
• Check for NullReference during the scan of InitializeComponent(), on reading a text from the resource file.
  

• Controls scan via source code (InitializeComponent) now detects use of AddRange() method to initialise - for example - a combo box.
  

• Tutorial files are now installed to the Shared Documents directory (instead of Program Files).
  
• New command in the Add-In's Help Menu opens the Windows Explorer in this directory.
  

• Fix error showing context menu on column headers and add exception handler to this function. (The previous version crashed!)
  

• Installation modified to grant users modify access to the global database file in common application data directory.
  (No program change. No version change.)
  

• Minor corrections to installation.
  

• Bug fixes editing the original text column in the controls grid.
  
• Bug fix in C++ source code scan (detecting function names).
  

• Global database now uses SQL Server Compact 3.5.
  
• If it is not already installed, then it is downloaded and installed automatically.
  
• SQL Server and Access are still supported, but the database files are no longer included in the installation.
  

• More exception handling on enumerating CodeElements.
  

• New grid component used
  
• All database access finally with ADO.NET
  
• Consistent handling of hidden items in both grids
  
• Immediate updates to .resx files
  
• Immediate updates to the function ml_UpdateControls()
  
• Toggle between two modes for column sizing
  
• Option to ignore specified modules
  
• Auto generated files ignored automatically
  
• Microsoft Translator button in translation memory dialog
  

• Additional error checking on the FileCodeModel.CodeElements property, which can cause a COMException (in the function FindFunction()).
  

• Bug fix in controls scan, for properties which have been explicitly deselected.
  
• Bug fix recognizing forms which derive only indirectly from System.Windows.Forms.Form.
  

• Truncate worksheet name to 31 characters and remove special characters during Excel export.
  

• Catch error on CodeElement.FullName.
  

• Automatically import texts from existing .resx files for new projects (with prior localization).
  

• Test for member variable for a control removed. Alternative code generation for this case also removed, because it did not always compile correctly. Controls with GenerateMember=False are not supported.
  

• Avoid COMException from EnvDTE.FileCodeModel.CodeElements at another place (see also 4.60.0038).
  

• Modified procedure to attach global database file to an existing instance of SQL Server. This is performed with the utility AttachGlobalDatabase, which now uses late binding to work with SQL Server 2005 or 2008, if one of these is installed.
  (No change to the Add-In itself.)
  

• Store global database connection in HKCU\Software\Jollans\MultiLang instead of HKCU\Software\Jollans\MultiLang2005 or ...\MultiLang2008:
  
  • for compatibility with the VB6 Add-In
    
  • for compatibility with possible future products (Excel Add-In?)
    
  • because differentiating between VS 2005 and 2008 was stupid anyway
    
• Install SQL Server datafile for global database (to Common App Data\MultiLang) and try to connect it to an existing SQL Server Express installation. If this succeeds, the Add-In is configured to use this database. Otherwise it continues to use the old Access database file.
  

• Fix for "Projectitem unavailable" error after removing a language.
  

• Add exception handler around EnvDTE.FileCodeModel.CodeElements, which can cause the COMException E_UNEXPECTED (aka. Catastrophic failure).
  

• Bug fix in the changes in previous version.
  

• Check constraints in ml_temp_xxx.xml files if a constraint error occurs.
  

• Additional error checking on opening the Add-In's Window.
  
• Registry entry GlobalDBUseConnectString changed to GlobalDBUseConnect for consistency with the setup program (which creates this entry) and with the VB6 Add-In.
  

• Another change to Infragistics support. Specifically scan into properties with the Attribute LocalizationCategory="Data", but not other values ("Appearance" or "Behavior"). This is more restrictive than the previous version.
  
• Fix handling of asp:literal tags with were not created the Add-In itself and contain additional attributes, in particular the Visible attribute.
  

• Bug fix for Infragistics support.
  

• A slightly better fix for Infragistics service release 20091.2023.
  

• Minor (and experimental) fix for Infragistics service release 20091.2023.
  

• Improved constraint check on reading project database from XML file.
  
• Identify menu items (and similar nested controls) by their own control name, rather than the indexed property in the parent control.
  
• New project setting to show menu items (and similar nested controls) as top level controls in the grid, rather than as child nodes under the parent control.
  

• Detect a language added to an Excel file (3-Worksheet format) when the new language is to the right of the comment column and prevent an error on importing the texts for this language.
  

• Check for localizable attribute on the Text property of an ASP tag in base classes.
  

• Incorrect and unnecessary handling of quotes in HTML text removed.
  
• Global database installed to Application Data directory (instead of Program Files).
  

• Minor update to the logic for detecting an unmanaged C++ project based on the Common Language Runtime support option. The options No support and /clr are now both handled as unmanaged code.
  

• Change to method of inserting Asp:Literal tag. Text is now placed between the start and end tags, rather than in the Text attribute.
  

• Option Untranslated Only added to Excel and Open Document export. If you select this option, strings are only exported if at least one translation is missing.
  
• New Single Worksheet Excel export with the features:
  
  • Multiply used strings are exported multiple times
    
  • Location column indicates where the string is used
    
  • Multiple usage column indicates how many times the string is used
    
  • Header is only one row (which is better suited to sorting the worksheet)
    
  • You can sort the worksheet on the String ID column to group multiple occurrences of the same String ID together
    
  • You can sort the worksheet on the Location column to group the texts according to where they are used
    

• Remove (Default) form the language selection list.
  
• Detect the title attribute in the page directive (for ASP content pages used in master pages).
  
• Bug fix updating the current text of ASP attributes from the grid.
  

• Support added for the Title of an ASP page, by defining the meta:resource key in the page directive.
  
• Check out temporary XML files, if they are under source controls (which I do not usually recommend).
  

• Check out XML project database, if it is under source control.
  

• Catch ConstraintException on reading project database from XML file. Remove duplicate records and try to set DataSet.EnforceConstraints to True.
  

• Minor fix to loading assemblies. Assembly.LoadFile replaced with Assembly.LoadFrom.
  

• Attempt to open assembly for referenced web control using Assembly.LoadFile, if Assembly.Load fails. Guess that VS has copied the referenced control into the bin directory.
  

• Fix to handling of web controls registered via the web.config file.
  
• Some restructuring to how assemblies registered via web.config or with a register directive in an ASP page are handled.
  

• Additional logic on closing Excel, to try to ensure that the Excel application is actually closed.
  
• Minor modification to colours used in Excel export, to avoid compatibility error saving to .xls format with Excel 2007.
  

• Additional checking for null reference in the function AddPropertyNodes, after some error reports.
  

• Bug fix in function Remove unused String IDs in the case where the project database is a .mdb file.
  

• Detect additional source code files, in particular code files which are children of other types of files, such as .xsd files.
  
• Additional localization of the Add-In itself.
  

• Fix to Advanced Copy function, to prevent the case where the option specified language is selected (for source or destination), but no language is selected.
  
• Catch AccessViolationException accessing ProjectItem.Properties when opening a designer window.
  

• Handle LANGUAGE LANG_NEUTRAL, SUBLANG_SYS_DEFAULT in a .rc file as meaning the neutral culture. (Previously, it generated LCID=0x800, which is not supported by the CultureInfo class.)
  

• Detect ASP Tags using binding syntax, e.g. Text='<%# Bind("title") %>', and treat them as non-localizable.
  

• Comment feature added
  
• Word wrap feature added
  
• Context menu command Goto Line-Break conflict
  
• Bug fix in .rc file scan for LANG_NEUTRAL
  

• Minor change to an error message for unmanaged C++ support.
  
• Updated help for unmaneged C++ support.
  

• Minor fixes to support for unmanaged C++ projects
  
  • Template paths for MlString module were stored incorrectly
    
  • Control ID -1 in dialog resources is treated identically to IDC_STATIC and replaced with a newly generated unique ID
    
  • Symbolic names are generated in the string tables in the .rc file (e.g. IDS_MULTILANG_181 instead of 181), although this is of no particular importance
    

• Minor fix for unmanaged C++ support.
  

• Minor fix to identify properties of Kliksoft controls. At present, this support will only work if you select alternative runtime support.
  

• Bug fix for selecting ASP properties when the grid is in the Flat list mode.
  

• First version with support for unmanaged C++, in particular MFC, projects.
  
• Some modifications to the HTML/ASP scanner:
  
  • All text between starting and ending tags for an ASP control, e.g. a label, is now associated with the text property, and may include formatting tags.
    
  • The formatting tags "ABBR", "ACRONYM", "ADDRESS", "B", "BIG", "CITE", "CODE", "DEL", "DFN", "EM", "FONT", "I", "KBD", "SAMP", "SMALL", "STRONG", "SUB", "SUP", "TT" and "VAR" are now left as part of the static HTML text for translation. This means that a translator will see these tags as part of the text. Previously, all tags were handled as a break between one block of text and the next.
    
  • Text within style tags is ignored.
    
• Goto line button enabled for HTML/ASP source windows.
  
• Goto line functionality added to context menu in source code and HTML/ASP windows (with the text Show in Multi-Language).
  
• Some speed improvements handling source code files.
  
• Expanded state of nodes in the HTML/ASP grid now saved to ml_temp_HtmlScan.xml (and restored after a new scan).
  

• Attempt to fix a NullReferenceException.
  

• Support for ASP server side comments added to ASP/HTML scanner.
  
• Bug fix in search dialog for ASP/HTML grid
  
• Partially implemented support for unmanaged C++ projects. Not yet ready for use!
  

• The default format for the project database is now XML and not an Access database.
  
• Bux fix assigning new StringIDs for the XML format.
  
• Tutorial projects updated to use the XML project database.
  

• Minor fix to saving the list of selected components.
  
• The support for runtime language switching now generates code to remove the handler for the language changed event when a form is disposed.
  
• Project properties dialog now has a second tab, where you can select how the project data is stored:
  
  • Access database, as in all previous versions
    
  • an XML file
    

• Special handling of inherited forms restricted to forms, whose base form is in the same project.
  
• List of selected components for Export to ResX and Rescan selected components saved (to ml_temp_ControlsScan.xml).
  
• More internal changes, moving towards replacing the project database with an XML file.
  

• Fix error opening the Language switching for web projects dialog.
  (Incorrect namespace "System.UI.Web" used instead of "System.Web.UI"!)
  

• Minor fix to the versioning of the project database schema, to correctly update a database from the most recent version for VS 2003, if a project is converted to VS 2005 or VS 2008.
  

• Support for hidden blocks in the source code, delimited by the comments MLHIDEON and MLHIDEOFF.
  
• The dialogs Export to ResX and Import from ResX now have a components list as well as a language list, so that you can select specific forms and usercontrols for the export or import operation.
  

• Minor bug fix on switching the alternative runtime support option, to prevent a (harmless) error dialog.
  

• Modified code generation for the function ml_UpdateControls() to handle inherited forms. The function ml_UpdateControls() in an inherited form now calls the equivalent function in the base form.
  

• Bug fix in source code scan for files with Unix style line breaks (LF only, not CR LF).
  

• Bug fix handling verbatim strings in C#.
  
• Bug fix handling extended properties (e.g. on ToolTip or HelpProvider controls) if the controls scan is performed by scanning the InitializeComponent() function.
  

• Close any resource editor windows before exporting resources.
  
• Automatically select the option "Determine Resource Names" if any Infragistics controls are detected in the project.
  
• New option "Clean up resource strings" to remove existing resource strings before exporting. (Not particularly recommended.)
  
• Option to set Localizable=True removed. This is now always performed for Forms and UserControls which have Localizable=False. (Determining if Localizable=False is faster since version 4.53.0024).
  

• Bug fix in the Filter by Regular Expression dialog. If you searched using an empty string, then an error occurred the next time the dialog was opened.
  

• Bug fix for possible NullReferenceException on attempting to switch the designer language via the language list on the Add-Ins toolbar
  

• First version with support for DevExpress XtraReports.
  

• Fix bug generated on selecting a source code string containing a single inverted comma.
  

• Exception handler added on closing hidden windows.
  

• Fix adding support for runtime language switching for the special case that a control has a static (shared) constructor.
  
• Some additional internal restructuring to the project database access (still preparing for bigger changes).
  

• Fix parameter error in log statment.
  

• Fix to ASP scan for empty attributes, e.g. Text="".
  
• Fix to resource fallback logic for ASP pages, if a rescan is performed whilst preview mode is active (i.e. the language of the designer has been changed).
  
• Special log file option for Excel import removed. The log information is now always stored in the standard log file.
  
• Some additional error checking before updating the project database.
  

• Same change as in 4.54.0002 applied to version 4.53.
  

• ASP scan uses a case insensitive search for the PropertyInfo objects describing the attributes of ASP controls. (The function Type.GetProperty() is case sensitive.)
  
  Note that whilst this fixes a problem with the ASP scan, I haven't tested whether the localized resources are actually detected at runtime, if the case does not exactly match the original case of the property.
  

• Internal restructuring of the access to the project database. At present, this introduces no change in functionality.
  

• Minor fix to assigning resource names to ASP controls.
  

• Some updates to handling multiple selection in the ASP/HTML grid.
  
• Improved logic to relocate the current item, if an ASP file has to be rescanned on the fly.
  

• Bug fix in the Filter with regular expression feature, if the match was against the complete code line and not just the text string. Previously, changes made to a file might not have been saved.
  
• Bug fix in operations on a multiple selection in the ASP/HTML grid. Previously, the operation might have broken off before completion.
  

• Bug fix on selecting multiple texts in the ASP grid. Previously, updates to an ASP file might not have been saved and a single file might have been opened multiple times.
  

• Check for the Localizable attribute on the properties of web controls in all base classes. For example, the HeaderText of a CheckBoxField is inherited from BoundField, which itself overrides the definition in DataControlField. The definition in BoundField does not have the Localizable attribute, but if we look in the base class DataControlField, we find that it does have the localizable attribute.
  
• Updates to the table GeneralIds in the project database. Column SourceCodeString renamed ContainsEscape (to reflect its actual usage). Column DontTranslate removed. Columns ContainsLineBreak and Comment added, but not yet used.
  

• Bug fix in SQL WHERE clause for boolean comparison. Automatic type conversion from boolean to string is language dependent, which led to a localized version of True or False in the SQL statement. This has been replaced with the syntax '<>0' or '=0' which should be safer.
  
• Minor fix to the initialsation of the list of languages, if you switch back and forth between different projects.
  
• More information written to the log file.
  

• Internal restructuring of the access to the project database. At present, this introduces no change in functionality. (Withdrawn.)
  

• Installation modified to specifically require Administrator privileges.
  
• On failing to load an assembly during the ASP scan, an error message is written to the output window, but the error dialog is not shown (might be a temporary change).
  
• Bug fix in the function "Determine Resource Names" required for Infragistics controls.
  
• Only show properties which have the IsBrowsable attribute. This is to avoid a particularly weird problem with the Infragistics UltraNumericEditor and UltraCurrencyEditor.
  
• New function to determine whether a form or UserControl has the localizable attribute, without having to load the designer window, speeds up a couple of operations.
  

• On deleting a translation via the context menu, and if the option "Store all strings in the global database" is selected, then the translation is also removed from the global database.
  

• Support added for ASP components referenced via a Register directive in the ASP file.
  
• Bug fix fetching translations from the global database for ASP pages.
  
• Changes to project database:
  
  • SourceScanResults and ControlsScanResults tables removed.
    The identical information is now saved in the XML files ml_temp_SourceScan.xml and ml_temp_ControlsScan.xml. These files contain temporary information and can be deleted.
    
  • ToolboxBitmapCache table removed.
    The identical information is now saved in a project-independent file in
    \Application Data\MultiLang.Net\
    
• Code generated in the function ml_UpdateControls() modified to support controls from Telerik (defined with local variables in InitializeComponent()).
  

• Additional exception handler on fetching toolbox bitmap. The controls scan should not be aborted if this unimportant feature fails.
  
• New logic on scanning controls via InitializeComponent, to open .resx file without using the designer window. This is almost certainly faster and may be more reliable.
  

• Advanced copy does not copy texts which are the only defined via resource fallback (shown in light grey).
  
• On inserting texts automatically from the global database, a text is not inserted if the identical text is already defined via resource fallback.
  

• Advanced copy function speeded up.
  
• Progress bar logic for controls scan simplified. The table ComponentInfoCache in the project database is now obsolete.
  

• Fix to saving changes to controls, following an Advanced Copy operation, in the case that the designer window for the component was not already open. (Note: The current implementation is intolerably slow, but at least it seems to work.)
  

• Restructuring of the scan of the function InitializeComponent() to handle concatenated strings.
  

• When the Advanced Copy function copies strings to a source code file, and the file has to be opened first, then ensure that it is saved before closing it.
  

• Show source code line in editor window after search or filter with regular expression operation.
  

• Bug fix storing texts to the global database, after changing the identification of an existing language in a project.
  

• Bug fix on importing from 3-Worksheet Excel format. If a string ID was changed in the source code worksheet, but the file was not already open in an editor window, then the source file would be updated, but then closed without saving the change.
  

• Bug fixes handling the drop down project list (due to the new item).
  

• Detect Forms and UserControls implemented with multiple partial classes. Only add the function ml_UpdateControls() to one of them.
  
• Support for custom cultures (new in .NET Framework 2.0). Custom cultures do not have a unique LCID.
  
• item added to the drop down project list.
  
• Translation memory extended, to allow you to search for additional words, not in the original text.
  
• Bug fix counting lines in ASP files, if lines end with LF only (and not CR-LF).
  

• Fix to a bug which could cause an error on adding alternative runtime support.
  
• Update to template file SelectLanguage.vb, required if Option Strict is selected.
  

• Do not use Add_Code subdirectory for the MlString module for Web Application projects.
  

• Copy correct MlString template file for Web Application projects.
  

• New dialog to add the Language-Selection Dialog, in particular with support for VB.NET projects which use the application framework.
  
• New option on Excel or Open Document export to include texts resulting from resource fallback.
  
• New handling of empty strings on Excel or Open Document import. An emtpy string is now interpreted as no translation, rather than an empty translation. If there is no translation, then the resource fallback mechanism will be used.
  
• Bug fix in the AODL library for cells with the table:number-columns-repeated attribute.
  

• ASP scan includes ASP files with no code behind file.
  (Note that the code scan still only scans the code behind file and not code embedded in the ASP file.)
  

• ASP scan handles attributes in single quotes.
  
• Bug fix on hiding empty ASP literal tag.
  
• Support for time limited license key added.
  

• Alternative Runtime Support dialog now detects the Localizable property of Forms or UserControls by reading the .resx files and not via the designer windows. This is faster and more reliable.
  
• Rescan selected components function fixed for ASP components. (Previously it always did a full scan.)
  
• Languages detected in .resx files are now added to the project automatically.
  
• Existing resource texts for ASP files are now always imported, unless there is already a text stored in the project database for the same property.
  

• Automatically import existing resource strings after scanning ASP files.
  (Initial version)
  
• Additional check added, for the case where the project database is referenced by the Visual Studio project file, but has actually been deleted.
  

• Bug fix for Visual Studio 2008. Previously, it was not possible to create a new project if the Add-In was loaded.
  
• Fix for error message on removing a project from the active solution when the Add-In is loaded, but no project has been selected.
  
• MLString template files for Smart Device projects updated.
  
• First version compiled using Visual Studio 2008.
  (This version can still be used with Visual Studio 2005.)
  

• Minor changes for Smart Device projects.
  
  • Alternative Runtime Support is no longer selected automatically. This was a hang over from Visual Studio 2003.
    
  • Bug fix in the template file MlString.vb.
    
  • Broken version template file SelectLanguage.Designer.cs corrected.
    

• Minor bug fix on exporting resource strings for a web project in the OnBuild event when using Visual Studio 2008. Under certain circumstances, Visual Studio 2008 would show a warning, that a file was about to be saved. If you selected cancel, then a COMException would be generated.
  

• New feature to import existing localization, which searches for function calls which load resource strings, imports the resource strings into the project database and converts the function calls into calls to ml_string().
  

• New templates for the MLRuntime project for Visual Studio 2008.
  
• The Add-In configuration for Visual Studio 2008 is now stored in a separate registry key (HKEY_CURRENT_USER\Software\Jollans\MultiLang2008)
  

• Export/Import as OpenOffice spreadsheet in the for OpenDocument .ods format. This feature uses the library AODL.
  
• 4.52.0001 is just an update to the help and the localization of the new dialogs.
  

• Bug fix detecting whether the MLRuntime project present in the solution, for the Runtime Language Switching feature.
  

• Bug fix scanning non-ASP files in ASP projects.
  

• Web Application projects are now recognized correctly.
  
• Informative error message if the Add-In is unable to open the Global Translations Database.
  
• Improved error checking in the case that the Global Translations Database is not available.
  

• Bug fix, for an error which caused the Localizable property to be reset to False after exporting resources for a Form or UserControl.
  

• Bug fix, for an error which caused resource strings for properties which are not translated to be excluded from even the original (non-localized) resource file.
  

• The Add-In no longer adds an ID attribute to ASP tags.
  
• If an ASP tag has an ID attribute, then the Add-In will use the same name for the resourcekey. Otherwise it will generate a resourekey in the form ML_nnnn. In particular, this applies to tags such as ListItem or TreeNode, which do not allow an ID attribute.
  
• The Add-In detects which ASP tags have a localizable Text attribute. Tags which do not have a localizable Text attribute cannot be selected in the grid.
  

• Resource strings are now referenced using the meta:resourcekey tag. No additional code must be generated to initialise the fields.
  
• New integrated scan of static HTML text and ASP controls. The results are presented in a single HTML/ASP tab.
  
• New HTML scan is faster and more reliable.
  
  • The ASP scan is performed by parsing the HTML source file and not (as previously) via the designer windows. This is significantly faster.
    
  • The ASP scan now handles template elements, for example in FormView or MultiView controls, which were previously not detected.
    
• Static HTML text is converted to an asp:Literal tag, so that the text can be read from a resource string. This replaces the previous method with a Span tag.
  

• New scan for resource names can be selected in the Export to ResX dialog. This provides improved support for controls from Infragistics.
  

• a completely new scan for texts in the HTML source, in addition to texts which are properties of ASP.NET controls
  
• an improved scan for properties of ASP controls
  
• a new Language Selection Web Control, which can be added to your project
  
• support for switching languages on an ASP.NET web page
  

• translation memory to show existing translations of similar texts
  
• multiple selection in the grids, so that multiple items can be hidden or selected for translation as a single operation
  
• user interface in French
  
• improved support for Smart Device projects in Visual Studio 2005
  

• Internal restructuring improves reliability
  
• Version 3 has no new features.
  

• Filter using regular expressions.
  

• New logic for the limitation in the unlicensed version (up to 50 translations from the global database, up to 100 translations in total).
  Naturally, these limitations do not apply to a licensed version.
  

• Some limited support for ASP.NET projects added.
  

• Global database of commonly used translations
  

• Structured three-worksheet Excel Import/Export
  

• Template file MlString.vb updated to handle solution names containing spaces.
  

• Speed improvement during source code scan.
  

• Runtime Language Switching extended to C++ projects.
  

• First version with support for Smart Device projects.
  

• Support for Runtime Language Switching.
  Change the language of the user interface at any time when the application is running.
  
• Quick initialisation of the grids from the project database.
  The Add-In can now reinitialize the two grids based on information cached in the project database. This means that it is not necessary to rescan the project each time the Add-In is used. You can enable this feature by turning off the automatic rescan in the project properties dialog.
  
• Hide properties in the controls tab.
  Properties listed in the controls tab may now be hidden. This is similar to mechanism for the source code tab (but at present not identical). Toggle the hidden state by clicking on the sun or moon icon. Show or hide 'hidden' properties via the "+-" drop down menu.
  Hide or show all properties with a given name, e.g. AccessibleDescription, via a context menu on the sun or moon icon in the controls tab.
  
• Select individual properties for translation.
  New check boxes in the controls tab allow individual properties to be selected for translation.
  Enable or disable translation of all properties with a given name, e.g. AccessibleDescription, via a context menu on the check box in the controls tab.
  
• New commands in the expand/collapse menu (for the controls tab only) to expand the tree to 1, 2, 3 or 4 levels.
  The expanded state of the nodes in the controls grid is now saved in the project database and restored when you restart the Add-In.
  
• Quick Export to resources.
  Using this option, the Add-In stores strings directly to the resource file, bypassing the controls. This may not work with all (third party) controls.
  (Starting with version 3, this is the only supported method).
  
• Handling of escape sequences in C# and C++ strings.
  
• Property filtering technique used to determine which properties will be read from the resource file. Properties which are not selected will not be read from resources. (Later removed).
  
• New command to remove all calls to ml_string() in the tools menu.
  

• Bug fix adding language containing inverted comma (e.g. People's republic of China)
  
• Source code scan now excludes the function InitializeComponent, rather than attempting to exclude the region of code generated by the forms designer.
  

• New commands "Goto next conflict" and "Goto next missing translation" added to the context menu.
  

• Font selection dialog now supports font size. Both font name and font size are stored on a per language basis.
  

• Bug fix for entering Asian characters, in particular Thai.
  
• Automatic source code scan can be disabled via the (new) project properties dialog. The results of the most recent scan are then loaded from the project database
  
• Bug fix for crash scanning very large projects
  

• Bug fixes in Search function.
  
• Controls scan logic updated to handle the Infragistics UltraWinToolbar control.
  

• Constraint added to project database to prevent duplicate translations for a single string ID and language ID.
  

• 'public class ml' changed 'internal class ml' in the template file MlString.cs.
  
• Character literals '\"' and '"' are now ignored.
  
• Error dialog shown if project database is read only.
  
• User interface disabled during long operations.
  

• Component VSUserControlHost.dll replaced with MLUserControlHost.dll, to fix initialisation problems on some systems. No change to the functionality.
  

• Support for Windows Forms Applications in C++ added
  (Visual Studio .NET 2003 only)
  

• Correction to handling of \" embedded in a C# string.
  

• Similar change at additional places in the program, to avoid an InvalidCastException with Components which are not "Components".
  

• Bug fix to handle forms containing "components" which do not inherit from Component, for example a DataSet. This error could be generated by the GridEx sample from Janus Systems.
  

• Minor fix to a problem exporting strings to resources, which occasionally caused languages to get mixed up.
  

• Error selecting "Advanced Copy" from context menu in title bar of grids fixed.
  

• C# support added
  

• Problems on first use of the Add-In with the error message COM object that has been separated from its underlying RCW can not be used and subsequent associated errors fixed.
  

• First public version of the Multi-Language Add-In for Visual Studio .NET, with support for Visual Basic applications.