TMEditX The Ultimate MSIX Package Editor plus TmMsixDeploy
To Documentation Index
TMEditX Command Line Options and Automation
TMEditX now supports a command line interface to automatically analyze and update your package. This may be the simplest way to create packages yet! Just run the command line against each package and the software will determine the right thing to do without further input in most cases.
It opens and analyzes the package and automatically applies all of the detected fixes. If the PSF is indicated, it always adds the FileRedirection, DynamicDll, and RegLegacy fixups using the most generous configurations to improve the odds of compatibility. If need for the EnvVar Fixup was detected, that will be added too. All other of the fixes you normally see in the analyzer will also be applied.
Depending on the command line options you provide, it can also save your package into either MSIX or CIM form, or leave the package open for your review before you save it yourself.
The command line options include the following:
|/ApplyAllFixes||After the package is opened it will automatically apply all relevant fixes, plus those that might improve the odds of compatibility for older apps.|
|/UseDebugPsf||By default, the release build of the PSF is used, but this option tells the tool to apply the debug build when applying the PSF.|
|/UseTraceMonitor||Add the PSF, TranceFixup, and PSFMonitor. This option is not applicable if ApplyAllFixes is used.|
|/UseWaitForDebugger||If the PSF is added, the Debug version of the PSF will be used and the WaitForDebuggerFixup will be added. This will pause the target application before it can run, waiting for a debugger (like Visual Studio) to attach to the process. This is something developers might do with their code to debug.|
|/AutoSaveAsMSIX||After applying fixes, the package will automatically be saved as a MSIX package using the tool configuration. In most cases, you would have configured TMEditX to increment the build number and save in the same folder with the filename using the updated build number. If configured, the Publisher field will be updated to match the configured certificate and the package is also signed.|
|/AutoSaveAsCIM||After applying fixes, the package will be automatically saved as a CIM package. The tool will create a new subfolder under the folder containing the input package and save the CIM there. Tool configuration options for versioning are applied.|
|filename||If automation is to be used, the filename of the MSIX package to be opened is added to the command line.|
Examples of common usage:
|TMEditX||Just open the application without a package and take no actions.|
|TMEditX filename||Open the named MSIX package and analyze it. Not fixes are automatically applied.|
|TMEditX /UseTraceMonitor /AutoSaveAsMSIX filename||Open the named MSIX package, analyze it, but only add the Launcher, TraceFixup, and PsfMonitor. Save and sign the package appropriately.|
|TMEditX /ApplyAllFixes /AutoSaveAsMSIX filename||Open the named MSIX package, analyze if, apply all fixes for compatibility, save and sign the package appropriately.|