From:	John Delo (Exchange)
Sent:	Tuesday, November 16, 1999 8:30 PM
To:	Alex Armanasu (Exchange)
Cc:	NTW Migration Services Team; Chris Steck (Exchange); Michele Freed (Exchange); Murthy Srinivas (Exchange)
Subject:	RE: Odyssey DSM Next Steps Mtg Mins.
I put updated tools and setmgr.msi on \\jdelo3\public\state, fixing minor bugs, incorrect schema file reference (should be SmSchema.xml), INI file handling, and a decompiler that regenerates the XML manifest (useful after merging multiple XML pieces).

What isn't obvious is that you don't need to register the compiled manifest - just specify it's name on the command line of settings.vbs (the default extension is .wsc). Registration isn't supported in settings.vbs anyway, and this special provision will likely become permanent - I will make that clearer in the command-line help.

So the procedure would be, given your manifest named foo:
1. Generate and refine the manifest foo.wsm
2. Compile using WsmComp foo (same as WsmComp foo.wsm foo.wsc), fixing any errors
3. Check the settings by using Settings foo or you may also specify individual settings as the 2nd arg, and updated values as the 3rd arg
4. Backup the settings using Settings foo /a foo.wsb  (default extension for the archive file will be fixed in a future release)
5. Transfer the archive file and either the original or compiled manifest to another machine
6. Compile the manifest if necessary, and restore using Settings foo /a /r foo.wsb
7. Check the settings using the tool or peeking the registry.

Currently the state store is also XML, but with a different schema, not terribly efficient, but very useful during development and testing. SInce the archive file is generated using MSXML.DLL, it comes out as a single line. You can view it formatted nicely using the tool ShowXml.vbs