Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio
All postings are provided AS IS
with no warranties, and confer no rights. Additionally, views expressed
herein are my own and not those of my employer, Microsoft.
A customer posted a bug report on my blog indicating that DUAScriptGen was incorrectly marking registry values that should be under HKEY_CLASSES_ROOT as HKEY_LOCAL_MACHINE. After investigating this scenario, I found that recent Windows XP Embedded hotfix release notes are formatting the registry information in a new way, which was causing the parsing logic in DUAScriptGen to report incorrect data. I have posted an updated version of DUAScriptGen (v1.1.0004) that will correctly parse registry data in both the old format and the new format. If you are using DUAScriptGen to generate DUA Script (DUS) files for any recent Windows XP Embedded hotfixes, please update to this new version or you may end up setting incorrect registry values in your deployed runtimes.
As always, please let me know if you see any additional problems with DUAScriptGen.