When I joined the Windows Embedded team a few months ago, I set out to learn about my team’s features, and one of the first things I started working with was Device Update Agent (DUA). I found the documentation very helpful, but felt a lot of pain trying to use Notepad as an IDE to create DUS scripts and get them to compile. I started thinking about some way to create a tool to hide the details of the script syntax from the user to make it easy to create and compile update scripts. Then I started talking to folks and found out that Mike Hall had already coded up a demo app that did exactly that. So for the past few weeks I’ve been working with him to finish implementing functionality, fix bugs, add a few features, and of course test it out.
We’ve finally got something that we’re ready to unveil to everyone. Click on the image below to download the DUAScriptGen.exe tool and try it today! You will need to have the .NET Framework 1.1 installed on your machine for it to work correctly since we wrote the tool in C#.
Here is a list of the cool things that the tool can do:
- Import the information in an XP Embedded QFE .RTF file to auto-generate script file – you can download the .RTF files on the same page as each of the QFE’s for XP Embedded (http://msdn.microsoft.com/embedded/downloads/xp/default.aspx)
- Drag/Drop files onto the application (or use the import button) to add additional files to the script
- Location setting for files – set individual files to specific folders on the target device (folders will be created if they don’t exist)
- Drag/Drop .REG files (or use the import button) to add groups of registry keys to the script
- Add specific .REG keys through DUAScriptGen UI
- Specify commands to execute as part of a script
- Specify the polling location, local DUA directory, and the name of the next script to poll for when an update completes
- Optionally reboot at the end of an update
- Reload scripts previously created by DUAScriptGen and modify them and recompile
Mike and I are really excited about this tool, and we hope that it will help folks more easily use DUA in their XP Embedded images. We would love to hear your feedback – bug reports, additional feature suggestions, usability improvements. Please post comments on either of our blogs….