ChangeLog

System Information Gathering Tool Change Log

12/4/2010: Version 1.2.17

Enhancements/Changes:

• There were a number of cosmetic issues addressed; most of these were issues where the wrong information displayed in a particular area.
• Basic upload functionality was added to the GUI portion of the application. You can now select "File" -> "Upload to UNC Share...". This will upload the current evaluation to the given server share.

A few notes on this. 1) This relies on your current credentials; and 2) There isn't enough error checking on the input aside from including required slashes at the beginning and end of the given path.

11/12/2010: Version 1.2.0

Tickets Addressed:

Ticket 2: You can now run the application via CLI
Ticket 12: The application will now explicitly try for a read-lock giving a better ability to get files that may have thrown this error before.
Ticket 13: The custom WMI method has been cleaned up and no longer throws so many exceptions
Ticket 15: You can now load a settings file via the GUI allowing for changes to the settings without relaunching the application
Ticket 16: The issue where help stopped working has been corrected; for the time being, the application will now pull up the SourceForge-based wiki-entry that explains the settings.xml file.
Ticket 17: Registry information is now parsed better to ensure it displays as expected.
Ticket 18: (Refer to ticket 13)
Ticket 20: Additionally checking added to ensure that a notice is displayed when this situation occurs.
Ticket 21: You can now query service information with a setting in the Settings.XML file
Ticket 22: The application will now launch regardless of a missing settings.xml file.
Ticket 23: The opening/closing of the settings.xml file is handled better allowing you to update and reload the settings.xml file while the application is running.
Ticket 25, 26, 27, 28: These are all cosmetic updates that were applied to make a few items look better or respond better.

Additional Enhancements/Changes:

• There were numerous changes to the code mostly towards using Static classes as there wasn't any need to initialize an object to perform these queries. Additionally, the structure of the code was changed - largely to accommodate the CLI additions. Basically, a "shared" class was created and the background classes were placed in their own namespace. Functionally of the application doesn't change because of this.

• The various settings in Settings.XML can now be placed within any tab of the application and it will be displayed there unlike the previous version where many core settings could not be relocated. Additionally, there is now an application control section within the settings file that allows you to turn off tabs that you don't need or rename the tabs to something more appropriate for the information you are displaying there.

Other notes:

I will test the application as best I can, but I need independent testers to make this more worthwhile - or someone needs to buy me the lab I've always dreamed of... At any rate, I'll do what I can to break the application and clean up any major bugs I can find. I still intend to release 1.2.0 by the end of this month before switching focus to more long-term goals for this project.

11/4/2010: Version 1.1.0

Tickets Addressed:

Issue 1. The application now accepts a new parameter via the 'settings.xml' file: <enumfile path="" file="">. This permits the gathering of information about a file, or multiple files within a given directory, including:</enumfile>

 * Creation Time
 * Last Modified Time
 * Company
 * Comments
 * Version
 * Size
 * Description

Issue 7. Copy and "select all" functionality has been added to the application. The only oddity here is that you need to ensure one of the browser controls is the active control or the commands won't seem to work.

Issue 8. Bug Fix: Previous to this version, Binary values stored in the registry were not returned correctly. The bytes will now be converted to a string display.

Issue 9. Bug Fix: Previously, registry returns containing commas in the value were not displayed correctly. This should no longer be an issue.

Issue 10. Bug Fix: If an environment path was used to locate a file (such as %systemroot%), it was not translated. It will now be translated when dealing with the "runcmd", "file", and "enumfile" settings.

Additional Enhancements/Changes:

• The GUI tab "Command Output" has been changed to "Misc. Output".
• The 'settings.xml' node related to command output was renamed from "command" to "misc" to match the new GUI naming.
• A core part of the code (form1.cs, where most of the magic happens) was cleaned up a bit to make it easier to find things.
• Help file documentation within the application was updated to reflect the changes above.
• GIT is now being used to provide code updates on each minor change.

Other notes:

There were a number of things that weren't included in this release that I'll be working on for future releases. Additionally, there are some places within the code that I feel could be made more efficient. And I've had a number of new ideas that I may jot down and start working towards. That being said, it should be a little while before 1.3 is released, depending, and I will be focusing more on fixing various little things that I've noticed and any bug that gets brought to my attention.

11/1/2010: Version 1.0.0

• Includes initial help dialogs.