Packages
We ship both Software deployable packages and Unified packages, to suit all possible deployment scenarios.
LCS
Our packages are available directly in your projects LCS solutions via invitation.
If you haven't been invited, please reach out to your account manager and request for an LCS invitation.
See Deploy from LCS
Software Deployable Packages
A Software deployable package is a compressed zip file containing application metadata, binaries, and source code updates. It used to be the standard format used to deploy custom X++ code, platform hotfixes, and ISV solutions across Microsoft Dynamics 365 environments.
The following software deployable packages are available for download:
Unified Packages
Unified Package is a deployment format used for modern Unified Developer Environments (UDE) and Power Platform-integrated systems. It bundles X++ customizations, Dataverse solutions, and metadata into a single zip file for deployment across Dynamics 365 environments.
The following unified packages are available for download:
See Deploy to UDE
Our unified packages contains the same Software Deployable Packages as Zip file, with additional Power Platform scaffolding.
Package conversion
Software deployable packages can easily be converted into Unified packages using the Modelutil command line.
ModelUtil.exe -convertToUnifiedPackage -file="SOFTWARE_DEPLOYABLE_PACKAGE" -outputpath="UNIFIED_PACKAGE"
You can locate ModelUtil.exe inside your local packages bin directory. For standard installations, this is typically located in:
C:\AOSService\PackagesLocalDirectory\bin
Checksums
Verifying a download's checksum is a crucial security and data integrity step. It acts as a digital fingerprint for a file, confirming the software is authentic, has not been tampered with by attackers, and wasn't corrupted during the download process before you run or install it.
Why You Should Verify Checksums ?
- Detecting File Corruption:
Network interruptions or unstable connections can sometimes corrupt files during download. A broken installer or operating system ISO can lead to frustrating installation errors later. Checksums ensure the file you saved is structurally identical to the file on the server. - Preventing Tampering and Malware:
If you download software from a third-party mirror site or if a primary website is compromised, attackers can replace the original program with a malicious one. Because cryptographic hash functions like SHA-256 produce a completely different output if even a single byte of a file is changed, verifying the checksum ensures you aren't installing malware.
Find the Original Checksum
Locate the hash value provided on the our official download page (labeled SHA-256 Checksum). Keep this page open, or copy the string to your clipboard.
Generate Your File's Checksum
Open the terminal and use one of the following built-in commands: Windows > Open > PowerShell or Command Prompt, navigate to the folder where your file is saved, and run
(Get-FileHash "FILENAME" -Algorithm SHA256).Hash
certutil -hashfile "FILENAME" SHA256
Compare and Verify
Compare the resulting alphanumeric string generated by your terminal to the official checksum you found in the first step.
- If they match: Your file is authentic, completely downloaded, and safe to use.
- If they do not match: The file may have become corrupted during the download, or it was tampered with. Delete the file and re-download it from the official links