Introduction
Installing and updating packages in the development environment is a common activity in Microsoft Dynamics 365 Finance. To ensure a smooth deployment, it’s important to properly remove old packages and install the new one without conflicts.
This blog explains the step-by-step process followed in a real-time development scenario.
Step-by-Step Process
Step 1: Verify the Package
- Identify the package provided
- Note the exact package name to avoid confusion.

Step 2: Remove Existing Package from Source Control
- Go to the trunk/main branch.
- Check if a package with the same name already exists.
- If it exists, delete the package.
Step 3: Move Changes to Pending
- After deletion, the package will appear under pending changes in source control.
Step 4: Check-In Changes
- Check in the pending changes to the main branch.
- This ensures the old package is completely removed from version control.
Step 5: Clean Local Package Directory
- Restart IIS service.
- Open Visual Studio → File Explorer.
-
Navigate to:
K:\AosService\PackagesLocalDirectory - Delete the existing package folder manually.
This step ensures there are no leftover files from the old package.
Step 6: Download and Extract New Package
- Download the new deployable package.
- Extract it to a local folder (e.g., Downloads).
Step 7: Install the Package via Command Prompt
- Open Command Prompt as Administrator.
-
Navigate to the extracted folder, for example:
C:\Users\<YourUser>\Downloads\AXDeployablePackage_XXXX -
Run the following command:
AXUpdateInstaller.exe devinstall
Step 8: Monitor Installation
- The installation process consists of multiple steps (usually 5 stages).
- It may take some time to complete.
- Wait until the process finishes successfully.
Step 9: Verify Package in Main Branch
- After installation, the package will be available in the main branch.
Step 10: Check-In Final Changes
- All updated files will appear under pending changes.
- Review and check in the changes to the main branch.
Best Practices
- Always remove the old package before installing a new one
- Restart IIS to avoid caching issues
-
Clean the
PackagesLocalDirectoryto prevent conflicts - Verify pending changes before check-in
- Ensure proper version control practices are followed
Conclusion
Proper package installation in Microsoft Dynamics 365 Finance requires careful handling of existing files, source control, and deployment steps. Following this structured approach helps avoid conflicts and ensures a smooth development experience.
No comments:
Post a Comment