RegXML Bugs & Planned Enhancements
[an error occurred while processing this directive]
RegXML:
usage |
download |
bugs & enhancements |
history |
license
Known Bugs / Planned Enhancements:
Last Updated August 26, 2001
As of version 1.4:
Known Bugs:
- When generating parent key XML, Class is ignored (Note that this is not a problem for importing these XML files, as long as the target registry already has these keys - the Class will not be deleted or changed. This is only an issue for importing such an XML file into a registry which does not have these keys already, and only if the Class should be non-blank.)
- Does not currently hold security information about particular keys under Windows NT
- Very large string values cause "more data available" error when reading in from an input file
Planned Functional additions:
- Provide some kind of transactional rollback capability - if something goes wrong during an import, rollback the entire import
- Handle other non-REG_SZ and non-REG_DWORD value types
- Provide option to pipe all errors into a separate file
- Provide option to log all actions taken during an import
- Provide option to warn/ask when overwriting existing values
- GUI interface add-on (the command-line interface should always be available for remote/unattended operation)
- Make the command-line switches case-insensitive
- Include the RegXML version number in the XML format specification for future backwards compatibility
- Provide access to remote registries (on other computers within the same network)
- Allow hex values for DWORD values in XML, including option to generate XML with hex values
- Allow wildcard values for InputFile
- Improve error descriptions
Planned Internal Code Changes:
- Include expat as a static library to avoid version collisions and easier installation
- Improve code comments
- Make helper classes threadsafe
If you have any other ideas, or would like to report problems, please tell me: software@eshayne.com.
RegXML:
usage |
download |
bugs & enhancements |
history |
license