This looks like a great tool, Bob, but I have a question. Can you tell us a little about how it handles the Windows Special Folders, a.k.a. Shell Folders? These are the folders referenced in the ShellFolders and UserShellFolders keys in the registry, some of which are represented by environment variables like ALLUSERSPROFILE, APPDATA, CommonProgramFiles, LOCALAPPDATA, ProgramData, ProgramFiles, SystemDrive, SystemRoot, TEMP, USERPROFILE.

Will Repackager prefer the variable name (e.g. %SystemRoot%) over the fixed path name (e.g., C:\WINDOWS) in every reference?

Will it use other environment variables like USERNAME and COMPUTERNAME?

How would it represent a reference to a file stored in the user's "My Documents" folder?

I know I'll figure this out eventually, once I've used Repackager on a few hundred packages. (Just kidding: only a few dozen.) But I'd love to hear from you about how this works internally, or how you intend it to work.

Thanks. Sande
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


You should see the special folders identified with their property values as you'd expect. As this is a simple repackager without editing capabilities, you cannot use it to substitute environment variables in paths-- however you may of course do so with a tool like InstEd (which is recommended for any desired edits/customizations). If you should see that something is not being referenced as you believe it should, please let me know and we can see about addressing any such things in a future release.

On a related note: recipe files utilize environment variables to best ensure compatibility between systems.
Answered 02/02/2009 by: bkelly
Red Belt

Please log in to comment