- 4.0 out of 5 stars Useful tool for cloth doll makers and craft workers alike. Reviewed in the United Kingdom on November 4, 2020. Color: 6/Pkg Verified Purchase.
- V3 HAN Tools: A Collection of Tools Targetting 3000/4000 Series Slim/Superslim To Allow OFW Package Manager and More. PS3Xploit Tools v3.0.3. 20200331 - ADDED SUPPORT FOR 4.86 HFW (Hybrid Firmware) thanks joonie/habib!. 20190931 - ADDED SUPPORT FOR 4.85 HFW (Hybrid Firmware) thanks joonie/habib!
A modern web frontend making aria2 easier to use (all-in-one version) arm-linux-gnueabihf-binutils-2.34-3-x8664.pkg.tar.zst A set of programs to assemble and manipulate binary and object files (arm-linux-gnueabihf).
| Developer(s) | Apple Inc. |
|---|---|
| Stable release | |
| Operating system | macOS |
| Type | IDE |
| Website | Apple Developer |
The Apple Developer Tools are a suite of software tools from Apple to aid in making software dynamic titles for the macOS and iOS platforms. The developer tools were formerly included on macOS install media, but are now exclusively distributed over the Internet. As of macOS 10.12, Xcode is available as a free download from the Mac App Store.
Applications[edit]
Applet Launcher[edit]
A graphical interface for Sun's Java Plug-in, which aids developers by demonstrating how Java applets perform on macOS. Provides tools to adjust the performance, behavior and user experience in applets in development.
Audio Unit Lab[edit]
A graphic presentation of audio units helping software developers to examine their results in decibels. AU Lab can be used to test audio units, conduct live mixing, and playback of audio content. Audio units are controlled visually with the audio unit's graphic interface and touch screen.
Computer Hardware Understanding Development Tools[edit]
A set of software tools, collectively Computer Hardware Understanding Development Tools (CHUD Tools) measure software performance on macOS, to aid in optimizing. Also provides hardware system benchmarks
Core Image Fun House[edit]
Used in testing Core Image units, which function similar to Adobe Photoshop filters. Each has a specific action, with parameters customize the action. Showcases Core Image, a technology introduced in Mac OS X 10.4, supported by newer graphic hardware.
CrashReporterPrefs[edit]
A developer utility for setting report parameters for Apple's Crash Reporter application.
- Basic: Shows a dialog asking the user what to do.
- Developer: Provides additional debug info and automatically shows the mail to Apple window.
- Server: Runs silent, but keeps all the logs.
- None: Disables the dialog prompt. Crash reports are neither displayed nor logged.
FileMerge[edit]
A staple of macOS's developer tools since the days of NeXTSTEP, FileMerge graphically compares two or more versions of a file. True to its name, FileMerge allows the user to easily merge the two or more versions into one file. The utility is often used to track changes to source code.
macOS's opendiff command provides the ability to launch FileMerge from the command line. The -ancestor parameter can be used for three-way merging.
Help Indexer[edit]
Creates an index file for the macOS built-in Help Viewer.
icns Browser[edit]
Views the resources for an .icns file, displaying the Mini, Small, Large, Huge, Thumbnail & Tile sizes in all color depths and masks.
Icon Composer[edit]
Icon Composer was an icon editor that does not have any editing features other than composing Apple Icon Image files and Windows ICO files. External editors must do all the image manipulation, then the results may be imported into the converter to create the finished icon. As of XCode 8.2, Icon Composer is no longer available in Additional Tools, as it cannot create high resolution icons. Apple recommends using the command-line utility iconutil, which ships with macOS [1].
Instruments[edit]
Instruments is a GUI for tracing framework DTrace from Sun's OpenSolaris. It is used to profile time usage, memory allocations, system activity, call trace analysis, GPU performance analysis, energy logging (on iOS devices) etc. [1]
Jar Bundler[edit]
Java tool that aids in packaging an application's component files into a single double-clickable application. Properties can be modified to optimize the code.
MallocDebug[edit]
Assistance for assessing memory usage and detecting memory leaks in programs.
Assesses an application's memory usage by monitoring a user as they interact with an application, which allows MallocDebug to build a memory profile that unfortunately is limited in size.
OpenGL Driver Monitor[edit]
Real time access to the inner workings of the graphics processing unit. Runs locally or over a network using Bonjour which is less likely to interfere with the statistics it is gathering with the exception of some disk fragmentation devices.
OpenGL Profiler[edit]
This tool assists developers in debugging and optimizing OpenGL usage under macOS.
Supported features:
- Launch or attach to an application
- Breakpoints and execution control
- Error detection including thread safety checks
- Scripts
- Buffer views
- Resource viewing/editing
- Statistics gathering
- OpenGL call traces with stack traces and timings
OpenGL Shader Builder[edit]
An integrated environment to develop and debug OpenGL GPU programs (Shaders) under macOS.
Features supported by OpenGL Shader Builder:
- Realtime entry
- Preview window with shaders applied to a textured plane, sphere or teapot
- Example shaders
- Syntax checking
- Debugging and analysis of vertex / fragment programs
- Export to Xcode
Note that this program is no longer recommended for editing GLSL shaders as 'GLSLEditorSample,' available as an example program, is generally regarded as superior.
PackageMaker[edit]
Creates application .pkg installer bundles for installing applications using the Installer application.
Pixie[edit]
A magnifying glass application for magnifying small sections of the computer's screen, centered around the mouse cursor, giving the user a detailed view of the screen, as well as the pixel coordinates of the mouse. Provides several levels of zoom, 'locking' the image under the mouse for closer examination, and saves the magnified image one of several formats. Helps ensure visual elements are aligned precisely.
Property List Editor[edit]
Edits application preference plist files. As of Xcode 4, Property List Editor is no longer included as a separate application and all editing of plist files is done within Xcode. The last stand-alone version was version 5.3 in Xcode 3.2.6.
Quartz Composer[edit]
A visual programming language for processing and rendering data. Using OpenGL, Core Image, Core Video, and other technologies to build an API and serves as a simple visual programming paradigm. Quartz Composer is a core technology of the macOS. Quartz Composer creations work in any QuickTime-aware application (beginning with Mac OS X 10.4), from the Quartz Composer application, or embedded into Cocoa or Carbon applications.
Quartz Composer has many similarities to Max/MSP although its primary usage is for graphical rather than audio processing. Offers the ability to construct interactive video compositions that react to audio or MIDI signals and can be played from any QuickTime aware application.
Pierre-Olivier Latour originally developed the predecessor to Quartz Composer under the name PixelShox Studio.[2]
A resurgence in interest in Quartz Composer has come about, as the Facebook design team has been showcasing their utilization of the program to prototype interactions that they couldn't have otherwise depicted with flat mockups in Photoshop.[3]
Repeat After Me[edit]
Optimizes the performance of the built-in text-to-speech software for macOS. Tests the operating system's phonemic translation engine, creates graphs of the generated tone, to visually adjust the intonation, and records samples for reference.
Shark[edit]
Shark is a profiler, used by software developers to optimize software programs on macOS. It samples software at set time intervals (or driven by hardware performance monitors events) taking snapshots of the stack, showing the functions which require more of the application's resources. Includes tools to analyze the data produced by a sampling run.Since Mac OS X 10.7, it is not on the Apple site any more and was replaced by Instruments.
Spin Control[edit]
Spin Control is a performance tool used for monitoring hang activity in software programs. The program gets its name from the spinning pinwheel on macOS.[4]
Discontinued as of Xcode 4.2.
Thread Viewer[edit]
Thread Viewer is a performance tool which graphically displays activity across a range of threads. It provides color-coded time-line views of thread activity and can display backtraces of activity at specific points in time. It was merged in Instruments app, and can be accessed via 'System Trace' instrument.
Xcode[edit]
Xcode is an integrated development environment (IDE) for macOS containing a suite of software development tools developed by Apple for developing software for macOS, iOS, iPadOS, watchOS, and tvOS. Xcode supports developing source code for the programming languagesC, C++, Objective-C, Objective-C++, Java, AppleScript, Python, Ruby, ResEdit (Rez), and Swift, with a variety of programming models, including but not limited to Cocoa, Carbon, and Java.
References[edit]
- ^'Track CPU core and thread use- Instruments Help'. Archived from the original on 2020-06-20.
- ^http://www.polhosting.info/web-archives/pixelshox_technology/Archived 2017-01-29 at the Wayback Machine PixelShox Technology
- ^'Design Prototyping with Quartz Composer'. Retrieved 13 February 2014.
- ^'Using Spin Control'.
External links[edit]
- Connection Tools – official site at Apple Inc.
Note
For UWP guidance on using this tool, see Create an app package with the MakeAppx.exe tool.
App packager (MakeAppx.exe) creates an app package from files on disk or extracts the files from an app package to disk. Starting with Windows 8.1, App packager also creates an app package bundle from app packages on disk or extracts the app packages from an app package bundle to disk. It is included in Microsoft Visual Studio and the Windows Software Development Kit (SDK) for Windows 8 or Windows Software Development Kit (SDK) for Windows 8.1. Visit Downloads for developers to get them.
The MakeAppx.exe tool is typically found at these locations:
- On x86: C:Program Files (x86)Windows Kits8.0binx86makeappx.exe or C:Program Files (x86)Windows Kits8.1binx86makeappx.exe
- On x64 in two locations:
- C:Program Files (x86)Windows Kits8.0binx86makeappx.exe or C:Program Files (x86)Windows Kits8.1binx86makeappx.exe
- C:Program Files (x86)Windows Kits8.0binx64makeappx.exe or C:Program Files (x86)Windows Kits8.1binx64makeappx.exe
There is no ARM version of the tool.
Using App packager
Note
Relative paths are supported throughout the tool.
To create a package using a directory structure
Place the AppxManifest.xml in the root of a directory containing all of the payload files for your app. An identical directory structure is created for the app package, and will be available when the package is extracted at deployment time.
Place all files in a single directory structure, creating subdirectories as desired.
Create a valid package manifest, AppxManifest.xml, and place it in the root directory.
Run this command:
MakeAppx pack /dinput_directorypath/pfilepath.appx
To create a package using a mapping file
Create a valid package manifest, AppxManifest.xml.
Create a mapping file. The first line contains the string [Files], and the lines that follow specify the source (disk) and destination (package) paths in quoted strings.
Run this command:
MakeAppx pack /fmapping_filepath/pfilepath.appx
To sign the package using SignTool
Create the certificate. The publisher listed in the manifest must match the publisher subject information of the signing certificate. For more info about creating a signing certificate, see How to create an app package signing certificate.
Run SignTool.exe to sign the package:
SignTool sign /a /v /fdhashAlgorithm/fcertFileNamefilepath.appx
The hashAlgorithm must match the hash algorithm used to create the blockmap when the app was packaged. With the MakeAppx packaging utility, the default Appx blockmap hash algorithm is SHA256. Run SignTool.exe specifying SHA256 as the file digest (/fd) algorithm:
SignTool sign /a /v /fd SHA256 /fcertFileNamefilepath.appx
For more info about how to sign packages, see How to sign an app package using SignTool.
To extract files from a package
Run this command:
MakeAppx unpack /pfile.appx /doutput_directory
The unpacked package has the same structure as the installed package.
To create a package bundle using a directory structure
We use the bundle command to create an app bundle at by adding all packages from contains a bundle manifest, AppxBundleManifest.xml, it is ignored.
Place all packages in a single directory structure, creating subdirectories as desired.
Run this command:
MakeAppx bundle /dinput_directorypath/pfilepath.appxbundle
To create a package bundle using a mapping file
We use the bundle command to create an app bundle at by adding all packages from a list of packages within contains a bundle manifest, AppxBundleManifest.xml, it is ignored.
Create a
Run this command:
MakeAppx bundle /fmapping_filepath/pfilepath.appxbundle
To extract packages from a bundle
Run this command:
MakeAppx unbundle /pbundle_name.appxbundle /doutput_directory
The unpacked bundle has the same structure as the installed package bundle.
To encrypt a package with a key file
Create a key file. Key files must begin with a line containing the string '[Keys]' followed by lines describing the keys to encrypt the package with. Each key is described by a pair of strings in quotation marks, separated by spaces or tabs. The first string represents the key ID and the second string represents the encryption key in hexadecimal form.
Run this command:
MakeAppx.exe encrypt /ppackage_name.appx /epencrypted_package_name.eappx /kfkeyfile_name.txt
The input package will be encrypted into the specified encrypted package using the provided key file.
To encrypt a package with a global test key
Run this command:
MakeAppx.exe encrypt /ppackage_name.appx /epencrypted_package_name.eappx /kt
The input package will be encrypted into the specified encrypted package using the global test key.
To decrypt a package with a key file
Create a key file. Key files must begin with a line containing the string '[Keys]' followed by lines describing the keys to encrypt the package with. Each key is described by a pair of strings in quotation marks, separated by spaces or tabs. The first string represents the base64 encoded 32-byte key ID and the second string represents the base64 encoded 32-byte encryption key.
Run this command:
MakeAppx.exe decrypt /ppackage_name.appx /epunencrypted_package_name.eappx /kfkeyfile_name.txt
The input package will be decrypted into the specified unencrypted package using the provided key file.
To decrypt a package with a global test key
Run this command:
MakeAppx.exe decrypt /ppackage_name.appx /epunencrypted_package_name.eappx /kt
The input package will be decrypted into the specified unencrypted package using the global test key.
Usage
The command line argument /p is always required, with either /d, /f, or /ep. Note that /d, /f, and /ep are mutually exclusive.
MakeAppx pack [options]/p/d
MakeAppx pack [options]/p/f
MakeAppx unpack [options]/p/d
MakeAppx bundle [options]/p/d
MakeAppx bundle [options]/p/f
MakeAppx unbundle [options]/p/d
MakeAppx encrypt [options]/p/ep
MakeAppx decrypt [options]/p/ep
Command-line Syntax
Here is the command-line common usage syntax for MakeAppx.
MakeAppx [pack|unpack|bundle|unbundle|encrypt|decrypt] [/h/kf/kt/l/o/no/nv/v/pfn/?]
MakeAppx packs or unpacks the files in a package, bundles or unbundles the packages in a bundle, or encrypts or decrypts the app package or bundle in the specified input directory or mapping file. Here is the list of parameters that apply to MakeAppx pack, MakeAppx unpack, MakeAppx bundle, MakeAppx unbundle, MakeAppx encrypt, or MakeAppx decrypt.
/l
This option is used for localized packages. The default validation trips on localized packages. This option disables only that specific validation, without requiring that all validation be disabled.
/o
Overwrite the output file if it exists. If you don't specify this option or the /no option, the user is asked whether they want to overwrite the file.
You can't use this option with /no.
/no
Prevents an overwrite of the output file if it exists. If you don't specify this option or the /o option, the user is asked whether they want to overwrite the file.
You can't use this option with /o.
/nv
Skip semantic validation. If you don't specify this option, the tool performs a full validation of the package.
/v
Enable verbose logging output to the console.
/?
Display help text.
Core Image Fun House[edit]
Used in testing Core Image units, which function similar to Adobe Photoshop filters. Each has a specific action, with parameters customize the action. Showcases Core Image, a technology introduced in Mac OS X 10.4, supported by newer graphic hardware.
CrashReporterPrefs[edit]
A developer utility for setting report parameters for Apple's Crash Reporter application.
- Basic: Shows a dialog asking the user what to do.
- Developer: Provides additional debug info and automatically shows the mail to Apple window.
- Server: Runs silent, but keeps all the logs.
- None: Disables the dialog prompt. Crash reports are neither displayed nor logged.
FileMerge[edit]
A staple of macOS's developer tools since the days of NeXTSTEP, FileMerge graphically compares two or more versions of a file. True to its name, FileMerge allows the user to easily merge the two or more versions into one file. The utility is often used to track changes to source code.
macOS's opendiff command provides the ability to launch FileMerge from the command line. The -ancestor parameter can be used for three-way merging.
Help Indexer[edit]
Creates an index file for the macOS built-in Help Viewer.
icns Browser[edit]
Views the resources for an .icns file, displaying the Mini, Small, Large, Huge, Thumbnail & Tile sizes in all color depths and masks.
Icon Composer[edit]
Icon Composer was an icon editor that does not have any editing features other than composing Apple Icon Image files and Windows ICO files. External editors must do all the image manipulation, then the results may be imported into the converter to create the finished icon. As of XCode 8.2, Icon Composer is no longer available in Additional Tools, as it cannot create high resolution icons. Apple recommends using the command-line utility iconutil, which ships with macOS [1].
Instruments[edit]
Instruments is a GUI for tracing framework DTrace from Sun's OpenSolaris. It is used to profile time usage, memory allocations, system activity, call trace analysis, GPU performance analysis, energy logging (on iOS devices) etc. [1]
Jar Bundler[edit]
Java tool that aids in packaging an application's component files into a single double-clickable application. Properties can be modified to optimize the code.
MallocDebug[edit]
Assistance for assessing memory usage and detecting memory leaks in programs.
Assesses an application's memory usage by monitoring a user as they interact with an application, which allows MallocDebug to build a memory profile that unfortunately is limited in size.
OpenGL Driver Monitor[edit]
Real time access to the inner workings of the graphics processing unit. Runs locally or over a network using Bonjour which is less likely to interfere with the statistics it is gathering with the exception of some disk fragmentation devices.
OpenGL Profiler[edit]
This tool assists developers in debugging and optimizing OpenGL usage under macOS.
Supported features:
- Launch or attach to an application
- Breakpoints and execution control
- Error detection including thread safety checks
- Scripts
- Buffer views
- Resource viewing/editing
- Statistics gathering
- OpenGL call traces with stack traces and timings
OpenGL Shader Builder[edit]
An integrated environment to develop and debug OpenGL GPU programs (Shaders) under macOS.
Features supported by OpenGL Shader Builder:
- Realtime entry
- Preview window with shaders applied to a textured plane, sphere or teapot
- Example shaders
- Syntax checking
- Debugging and analysis of vertex / fragment programs
- Export to Xcode
One notable feature is 'Export to Xcode'. A sample Xcode project is created with C source code to initialize OpenGL (using the GLUT library) and run the shader program.
Note that this program is no longer recommended for editing GLSL shaders as 'GLSLEditorSample,' available as an example program, is generally regarded as superior.
PackageMaker[edit]
Creates application .pkg installer bundles for installing applications using the Installer application.
Pixie[edit]
A magnifying glass application for magnifying small sections of the computer's screen, centered around the mouse cursor, giving the user a detailed view of the screen, as well as the pixel coordinates of the mouse. Provides several levels of zoom, 'locking' the image under the mouse for closer examination, and saves the magnified image one of several formats. Helps ensure visual elements are aligned precisely.
Property List Editor[edit]
Edits application preference plist files. As of Xcode 4, Property List Editor is no longer included as a separate application and all editing of plist files is done within Xcode. The last stand-alone version was version 5.3 in Xcode 3.2.6.
Quartz Composer[edit]
A visual programming language for processing and rendering data. Using OpenGL, Core Image, Core Video, and other technologies to build an API and serves as a simple visual programming paradigm. Quartz Composer is a core technology of the macOS. Quartz Composer creations work in any QuickTime-aware application (beginning with Mac OS X 10.4), from the Quartz Composer application, or embedded into Cocoa or Carbon applications.
Quartz Composer has many similarities to Max/MSP although its primary usage is for graphical rather than audio processing. Offers the ability to construct interactive video compositions that react to audio or MIDI signals and can be played from any QuickTime aware application.
Pierre-Olivier Latour originally developed the predecessor to Quartz Composer under the name PixelShox Studio.[2]
A resurgence in interest in Quartz Composer has come about, as the Facebook design team has been showcasing their utilization of the program to prototype interactions that they couldn't have otherwise depicted with flat mockups in Photoshop.[3]
Repeat After Me[edit]
Optimizes the performance of the built-in text-to-speech software for macOS. Tests the operating system's phonemic translation engine, creates graphs of the generated tone, to visually adjust the intonation, and records samples for reference.
Shark[edit]
Shark is a profiler, used by software developers to optimize software programs on macOS. It samples software at set time intervals (or driven by hardware performance monitors events) taking snapshots of the stack, showing the functions which require more of the application's resources. Includes tools to analyze the data produced by a sampling run.Since Mac OS X 10.7, it is not on the Apple site any more and was replaced by Instruments.
Spin Control[edit]
Spin Control is a performance tool used for monitoring hang activity in software programs. The program gets its name from the spinning pinwheel on macOS.[4]
Discontinued as of Xcode 4.2.
Thread Viewer[edit]
Thread Viewer is a performance tool which graphically displays activity across a range of threads. It provides color-coded time-line views of thread activity and can display backtraces of activity at specific points in time. It was merged in Instruments app, and can be accessed via 'System Trace' instrument.
Xcode[edit]
Xcode is an integrated development environment (IDE) for macOS containing a suite of software development tools developed by Apple for developing software for macOS, iOS, iPadOS, watchOS, and tvOS. Xcode supports developing source code for the programming languagesC, C++, Objective-C, Objective-C++, Java, AppleScript, Python, Ruby, ResEdit (Rez), and Swift, with a variety of programming models, including but not limited to Cocoa, Carbon, and Java.
References[edit]
- ^'Track CPU core and thread use- Instruments Help'. Archived from the original on 2020-06-20.
- ^http://www.polhosting.info/web-archives/pixelshox_technology/Archived 2017-01-29 at the Wayback Machine PixelShox Technology
- ^'Design Prototyping with Quartz Composer'. Retrieved 13 February 2014.
- ^'Using Spin Control'.
External links[edit]
- Connection Tools – official site at Apple Inc.
Note
For UWP guidance on using this tool, see Create an app package with the MakeAppx.exe tool.
App packager (MakeAppx.exe) creates an app package from files on disk or extracts the files from an app package to disk. Starting with Windows 8.1, App packager also creates an app package bundle from app packages on disk or extracts the app packages from an app package bundle to disk. It is included in Microsoft Visual Studio and the Windows Software Development Kit (SDK) for Windows 8 or Windows Software Development Kit (SDK) for Windows 8.1. Visit Downloads for developers to get them.
The MakeAppx.exe tool is typically found at these locations:
- On x86: C:Program Files (x86)Windows Kits8.0binx86makeappx.exe or C:Program Files (x86)Windows Kits8.1binx86makeappx.exe
- On x64 in two locations:
- C:Program Files (x86)Windows Kits8.0binx86makeappx.exe or C:Program Files (x86)Windows Kits8.1binx86makeappx.exe
- C:Program Files (x86)Windows Kits8.0binx64makeappx.exe or C:Program Files (x86)Windows Kits8.1binx64makeappx.exe
There is no ARM version of the tool.
Using App packager
Note
Relative paths are supported throughout the tool.
To create a package using a directory structure
Place the AppxManifest.xml in the root of a directory containing all of the payload files for your app. An identical directory structure is created for the app package, and will be available when the package is extracted at deployment time.
Place all files in a single directory structure, creating subdirectories as desired.
Create a valid package manifest, AppxManifest.xml, and place it in the root directory.
Run this command:
MakeAppx pack /dinput_directorypath/pfilepath.appx
To create a package using a mapping file
Create a valid package manifest, AppxManifest.xml.
Create a mapping file. The first line contains the string [Files], and the lines that follow specify the source (disk) and destination (package) paths in quoted strings.
Run this command:
MakeAppx pack /fmapping_filepath/pfilepath.appx
To sign the package using SignTool
Create the certificate. The publisher listed in the manifest must match the publisher subject information of the signing certificate. For more info about creating a signing certificate, see How to create an app package signing certificate.
Run SignTool.exe to sign the package:
SignTool sign /a /v /fdhashAlgorithm/fcertFileNamefilepath.appx
The hashAlgorithm must match the hash algorithm used to create the blockmap when the app was packaged. With the MakeAppx packaging utility, the default Appx blockmap hash algorithm is SHA256. Run SignTool.exe specifying SHA256 as the file digest (/fd) algorithm:
SignTool sign /a /v /fd SHA256 /fcertFileNamefilepath.appx
For more info about how to sign packages, see How to sign an app package using SignTool.
To extract files from a package
Run this command:
MakeAppx unpack /pfile.appx /doutput_directory
The unpacked package has the same structure as the installed package.
To create a package bundle using a directory structure
We use the bundle command to create an app bundle at by adding all packages from contains a bundle manifest, AppxBundleManifest.xml, it is ignored.
Place all packages in a single directory structure, creating subdirectories as desired.
Run this command:
MakeAppx bundle /dinput_directorypath/pfilepath.appxbundle
To create a package bundle using a mapping file
We use the bundle command to create an app bundle at by adding all packages from a list of packages within contains a bundle manifest, AppxBundleManifest.xml, it is ignored.
Create a
Run this command:
MakeAppx bundle /fmapping_filepath/pfilepath.appxbundle
To extract packages from a bundle
Run this command:
MakeAppx unbundle /pbundle_name.appxbundle /doutput_directory
The unpacked bundle has the same structure as the installed package bundle.
To encrypt a package with a key file
Create a key file. Key files must begin with a line containing the string '[Keys]' followed by lines describing the keys to encrypt the package with. Each key is described by a pair of strings in quotation marks, separated by spaces or tabs. The first string represents the key ID and the second string represents the encryption key in hexadecimal form.
Run this command:
MakeAppx.exe encrypt /ppackage_name.appx /epencrypted_package_name.eappx /kfkeyfile_name.txt
The input package will be encrypted into the specified encrypted package using the provided key file.
To encrypt a package with a global test key
Run this command:
MakeAppx.exe encrypt /ppackage_name.appx /epencrypted_package_name.eappx /kt
The input package will be encrypted into the specified encrypted package using the global test key.
To decrypt a package with a key file
Create a key file. Key files must begin with a line containing the string '[Keys]' followed by lines describing the keys to encrypt the package with. Each key is described by a pair of strings in quotation marks, separated by spaces or tabs. The first string represents the base64 encoded 32-byte key ID and the second string represents the base64 encoded 32-byte encryption key.
Run this command:
MakeAppx.exe decrypt /ppackage_name.appx /epunencrypted_package_name.eappx /kfkeyfile_name.txt
The input package will be decrypted into the specified unencrypted package using the provided key file.
To decrypt a package with a global test key
Run this command:
MakeAppx.exe decrypt /ppackage_name.appx /epunencrypted_package_name.eappx /kt
The input package will be decrypted into the specified unencrypted package using the global test key.
Usage
The command line argument /p is always required, with either /d, /f, or /ep. Note that /d, /f, and /ep are mutually exclusive.
MakeAppx pack [options]/p/d
MakeAppx pack [options]/p/f
MakeAppx unpack [options]/p/d
MakeAppx bundle [options]/p/d
MakeAppx bundle [options]/p/f
MakeAppx unbundle [options]/p/d
MakeAppx encrypt [options]/p/ep
MakeAppx decrypt [options]/p/ep
Command-line Syntax
Here is the command-line common usage syntax for MakeAppx.
MakeAppx [pack|unpack|bundle|unbundle|encrypt|decrypt] [/h/kf/kt/l/o/no/nv/v/pfn/?]
MakeAppx packs or unpacks the files in a package, bundles or unbundles the packages in a bundle, or encrypts or decrypts the app package or bundle in the specified input directory or mapping file. Here is the list of parameters that apply to MakeAppx pack, MakeAppx unpack, MakeAppx bundle, MakeAppx unbundle, MakeAppx encrypt, or MakeAppx decrypt.
/l
This option is used for localized packages. The default validation trips on localized packages. This option disables only that specific validation, without requiring that all validation be disabled.
/o
Overwrite the output file if it exists. If you don't specify this option or the /no option, the user is asked whether they want to overwrite the file.
You can't use this option with /no.
/no
Prevents an overwrite of the output file if it exists. If you don't specify this option or the /o option, the user is asked whether they want to overwrite the file.
You can't use this option with /o.
/nv
Skip semantic validation. If you don't specify this option, the tool performs a full validation of the package.
/v
Enable verbose logging output to the console.
/?
Display help text.
MakeAppx pack , MakeAppx unpack , MakeAppx bundle, MakeAppx unbundle, MakeAppx encrypt, and MakeAppx decrypt are mutually exclusive commands. Here are the command-line parameters that apply specifically to each command:
MakeAppx pack [h]
Creates a package.
/halgorithm
Specifies the hash algorithm to use when creating the block map. Here are valid values for algorithm:
- SHA256 (default)
- SHA384
- SHA512
You can't use this option with the unpack command.
MakeAppx unpack [pfn]
Extracts all files in the specified package to the specified output directory. The output has the same directory structure as the package.
/pfn
Specifies a directory named with the package full name. This directory is created under the provided output location. You can't use this option with the pack command.
MakeAppx unbundle [pfn]
Unpacks all packages to a subdirectory under the specified output path, named after the bundle full name. The output has the same directory structure as the installed package bundle.
/pfn
Specifies a directory named with the package bundle full name. This directory is created under the provided output location. You can't use this option with the bundle command.
MakeAppx encrypt [kf, kt]
Creates an encrypted app package from the specified input app package at the specified output package.
Game Description When Jack Frost comes nipping at the nose and toes.it's time to come inside and get warm as you attempt to solve over 100 unique solitaire card layouts Jack Frost has created for you. Enjoy classical solitaire improved with a new game mechanic – collecting pairs of cards! Solitaire Jack Frost: Winter Adventures Awaken the Christmas spirits in this Solitaire fairy tale! Finally - it's Christmas time! We had to wait a whole year until the coziest of all seasons finally started again. This year, Jack Frost is granting us numerous levels of light-hearted Solitaire fun! Christmassy imageries and a snuggly atmosphere. Solitaire jack frost winter adventures crack. Believe in the power of frosty layouts and complete all of them in the game Solitaire Jack Frost: Winter Adventures 3! Cheerful Jack Frost continues his mission of giving the gift of. The happy adventure is beginning with Solitaire Jack Frost! A solitaire card game with winter layouts! Numerous bonuses and over 20 colorful trophies! Play for a few minutes or several hours in a row! Download Solitaire Jack Frost Winter Adventures HD Free and enjoy it on your iPhone, iPad, and iPod touch. The Christmas holidays are coming! And that means that jolly Jack Frost and his helper want to give everyone a fairytale season by awakening the spirit of Christmas! Jack has decided to spread frost all over and create 120 unique card.
/kf
Encrypts the package or bundle using the key from the specified key file. You can't use this option with kt.
/kt
Encrypts the package or bundle using the global test key. You can't use this option with kf.
MakeAppx decrypt [kf, kt]
Creates an unencrypted app package from the specified input app package at the specified output package.
/kf
Decrypts the package or bundle using the key from the specified key file. You can't use this option with kt.
/kt
Decrypts the package or bundle using the global test key. You can't use this option with kf.
Semantic validation performed by MakeAppx
MakeAppx performs limited semantic validation that is designed to catch the most common deployment errors and help ensure that the app package is valid.
This validation ensures that:
- All files referenced in the package manifest are included in the app package.
- An application does not have two identical keys.
- An application does not register for a forbidden protocol from this list: SMB , FILE, MS-WWA-WEB, MS-WWA.
Cached
This semantic validation is not complete, and packages built by MakeAppx are not guaranteed to be installable.
