VBXC Release history
Beta 3
Changes since last release:
- Optional byref parameters was not decorated with an @ in the XML file
- Configure soltion no longer asks about saving changes after pressing apply
- Fixed problems with expanding ''' when line continuations and attributes are involved
- When pressing ''' at the start of the first line of a code element the add-in now places any expanded template correctly
- Build XML Doc based on project configuration from the configure solution is now persisted between VS.NET sessions
- VBXC should no longer make VS.NET crash or complain about trouble getting an extender
- VBXC now is tested with and installs itself for VS.NET 2003
- The manual Build XML Comment file for solution now works if the setting GenerateXMLCommentsOnBuild is set to false
- VBXC now stores it's settings in a XML file in the users local ApplicationSettings folder instead of the registry to make copying of settings easier
- The manual "Build XML comment file for solution" crashed if the solution contained a database project
- The add-in now automaticaly puts the content of the description property of System.Web.Services.WebServiceAttribute into newly created stubs
- Possibility to only buld the XML comment file from the commandline using devenv (see documentation for more info)
- Possibility to query for and set any of the configuration options that VBXC provides from a macro or an add-in (see documentation for more info)
Click here to download beta 3
Beta 2.1
Changes since last release:
- You no longer get an error when trying to insert XML comment stubs (by pressing ''' followed by return)
- A message is now displayed instead of an error dialog if you try to use menu items that require that a solution is open
Beta 2
Changes since last release:
- The add-in does now produce an XML file with the name specified in the project configuration as the beta1 did
Beta 2 pre-release 4 (non-public release)
Changes since last release:
- Fixed the loop that should probit invalid extender instances to throw the error "The Extender instance is no longer valid."
- The error dialog now displays the correct log-path for the error log file.
- Settings is now saved in a new location in the registry, this means that all old settings is lost.
- Added description on settings in the general config window
- Marked default values in the general config window so that they are non-bold if set to the default setting
- Warnings related to code elements are no longer written to the logfile
- Added more detailed error information to errors related to getting codelines
- Changed default value of LookForRegularCommentIfNoXMLCommentFound to false
- Constructors no longer get's a element in the autogenerated stub
- Added username, machinename and name of element to the XML description of a element (used for templates)
- Added a new configuration parameter GenerateXMLCommentsOnBuild that makes it possible to disable the build integration VBXMLDoc provides
- Made a test-bed application for templates
- Added a configuration parameter that makes it possible to disable the 'show tasklist on compile' feature
- Modified the logo during compile for non-VB.NET projects
- Now extracting descriptions from WebMethodAttribute's description argument and adding them to the summary tag (when creating the XML comment stub) and possibly to 'not documented' tags with modified template
- Now Extracting descriptions from ComponentModel.Description attribute and adding them to the summary tag (when creating the XML comment stub) and possibly to 'not documented' tags with modified template
- WriteOnly properties now don't get the Value parameter of the setter method in the parameter list of the autogenerated stub
- Added support for generating comments files for projects in current solution by selecting a menu item
- The add-in now tries to remove old menu items on first startup in order to fix broken menus
- The setup now upgrades existing installations
- Removed the extender for project configuration to remove current System.ExecutionEngineException problem
Beta 2 pre-release 3 (non-public release)
Changes since last release:
- A warning indicating a missing comment for comments with errors in them is now not generated
- The setting LookForRegularCommentIfNoXMLCommentFound now works
- Improved the performance of simple xml validation (now only uses a XMLValidatingReader instead of loading the fragment into a XML document)
- Improved performance of include processing (the add-in now uses a lightweight test to check if the XML fragment needs include processing or not)
- Improved the general speed of the XML documentation generation as the add-in now internaly uses a StringBuilder instead of a string to generate the XML document
- Improved performance of the XML extraction by adding caching to the retrieval of settings from the registry
- Improved and optimised the tasklist integration. It should now be quite a lot faster than the last implementation.
- Added more detailed logging to track down the ExecutionEngineException
Beta 2 pre-release 2 (non-public release)
Changes since last release:
- It now correctly locates the output assembly on web application and web service projects
- If pressing ''' followed by either return or arrow down on the first lines in a vb code file you no longer get an error
- If pressing ''' followed by enter in front of a class decorated with attributes using line continuation and/or classes that had inherits/implements lines no stub where created
- If pressing ''' followed by enter in front of a writeonly property you no longer get an error
- If building a comments file from a project that have writeonly properties you no longer get an error
- The add-in supports building from the command-line using the by using devenv with the appropriate switches
- The add-in could not extract comments from code files that where sub-items of other project items or where placed in folders
- The add-in crashed while extracting comments from a solution that used nested project structures (e.g. enterprise templates)
- The add-in crashed when selecting a project in the solution explorer that where not placed directly below the solution (e.g when using enterprise templates)
- The add-in where unable to extract comments from non-classes that used line continuation
- Reimplemented use of extenders in the XML comment extraction phase to improve error handling information
- Added logic for handling "Expired Extenders" up to 10 times before bailing out
- Added config parameter for creating only simple assembly descriptions in output XML file
- Added logic for creating a simple assembly description if the add-in was unable to open the output assembly
- Added support for extracting XML comments from enumeration members
- Added logo in build window when the add-in is activated
- Added about screen
- Added description text at the bottom of the General Settings screen
- Reimplemented storage of information in project file, it should not be added if not default values is changed, and should show a message to the user if the project file is under source control telling the user that he/she has to checkout the file before editing the properties on the file
- Add-in now manages to extract comments from classes decorated with attributes on the line above the class declaration
- Improved insertion of ''' on new lines etc. It now let's you insert new lines in the middle of text, and inserts ''' when you press return on the first line of a XML comment block
- Member variables that are withevents are now correctly marked as properties in the XML file because VB.NET generates a property for these in the resulting assembly
- Added support for templates on the autogenerated XML stubs
- Added simple validation of XML comments
- Added support for the include tag (requires that simple validation is turned on!)
- Added integration with the task-list so that it displays warnings generated during the compile process
- Not documented comments now only gets created on items that is checked for XML comments (based on visibility)
- Added support for templates on not documented comments
- Added dialog for configuring template settings
- Add-in now accepts empty lines between the XML comment and the commented element
- Add-in now also handles regular comments above elements as XML comments if no ordinary XML comment is found (can be switched off in the configuration)
- Added configuration item that let's the user disable all functioanlity the VBXMLDoc provides without unloading or uninstalling the add-in
Beta 1
Tor-Erik Hagen © 2002-2003