web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Deploying ISV solutions
Microsoft Dynamics AX (Archived)

Deploying ISV solutions

(0) ShareShare
ReportReport
Posted on by Jagadesh Babu Kolli... 50

Hi

We received 2 model files and one package (without source code) from our ISV. What is the best approach to deploy them?

Option 1:

  1. Model files - Install model on a dev machine, resolve conflicts and deploy it along with our custom packages
  2. package (without source code) - Deploy on each environment as a independent package

Option 2: Deploy package (without source code) + Install model on a dev machine, resolve conflicts and deploy it along with our custom packages

Option 3: Use Nuget to deploy packages - Is this a feasible option?

Please let me know your suggestions.

Thanks

Jag

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Joris dG Profile Picture
    Joris dG 17,780 on at

    I think the source models are clear what needs to be done. Install, resolve conflicts, check into source control. Done.

    For the runtime packages, we recommend you check them into source control as well after installing on one of the dev boxes. This has several advantages:

     1. other devs just need to sync them in

     2. no need to install on build VM if you need them there, source control will make sure they're there

     3. if you're using branching you could have different versions of the ISV in different branches

     4. you're sure you have the right combination of source and runtime from the ISV at any given time

    Additionally, we're planning to have a build option to include that ISV's binary package into the build output. That way you only have 1 package that contains everything - your custom code as well as any third party binaries.

    Obviously, you're option 1 works just as well. Not sure how option2 is different from option1?

  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 304,553 Super User 2026 Season 1 on at

    Hi Jag,

    If you got a solution from an ISV, the best would be to deploy the package. If this ISV was developed using extensions only (preferred way!!) you should not have any conflicts. We deliver our solutions only as deployable package.

    The model files are only required when you want to view the source code.

  • Jagadesh Babu Kollipara Profile Picture
    Jagadesh Babu Kolli... 50 on at

    Thanks Joris, for the detailed response.

    In my Option1, runtime packages are installed as separate package from our package  and Option2- Deploy runtime package in a dev box and check DLLs in to source control and update our build definition to include these dlls in our package. But from your answer looks like this is not possible now but planned in the future. Could you please confirm my understanding.

    Is it a good idea to consider Nuget package manager for managing ISV solutions (Dlls i.e., runtime packages)?

  • Suggested answer
    Joris dG Profile Picture
    Joris dG 17,780 on at

    Since the build expects the DLLs to be in certain places you can't easily use NuGet today, unfortunately.

    As of Platform Update4 it supports runtime packages checked into source control. There's a hotfix for update3 and update2 as well if you want to do it on those older versions. As of Platform Update6 there's even more features in that it will "repackage" the runtime packages in the deployable package the build creates - so you have one deployable package with your compiled code as well as any source controlled runtime packages.

    The documentation for this is currently under review so hopefully gets published this week or next.

  • Suggested answer
    Joris dG Profile Picture
    Joris dG 17,780 on at

    FYI: docs.microsoft.com/.../manage-runtime-packages

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
CP04-islander Profile Picture

CP04-islander 39

#2
Michel ROY Profile Picture

Michel ROY 14

#3
imran ul haq Profile Picture

imran ul haq 8

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans