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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

Apply deployable package to Cloud Hosted DEV VM

(1) ShareShare
ReportReport
Posted on by 382
Hello everyone,
 
I applied the deployable package to the dev machine, if I download all the source code from Azure DevOps, compile those source code into binaries, will it wipe out what the object I deployed before via the package?
 
Thanks,
I have the same question (0)
  • Suggested answer
    Martin Dráb Profile Picture
    237,807 Most Valuable Professional on at
    If you're talking about the same module, then yes, creating new binaries by compiling source will overwrite binaries you've installed from the deployable package.
  • Suggested answer
    Navneeth Nagrajan Profile Picture
    2,407 Super User 2025 Season 2 on at
    Hi,
     
    Suggestion:
    1. You need not put so much efforts to deploy a package to the dev machine (Unless you are moving a deployable package to a local DEV and TEST category VM). As Martin rightly said, your binaries will be over ridden. You can instead use Azure DevOps Git or TFVC and add the development component and have it synced on your deployable dev machine.
     
    2. Export your project and later, use the Import project option from the Dynamics 365 menu in Visual studio to import your components onto your solution. Post import, you can do a local build of the model that the object belongs to.
     
     
    Happy to answer questions, if any.
     
  • Martin Dráb Profile Picture
    237,807 Most Valuable Professional on at
    I see absolutely no reason for importing projects in this case and I don't think suggesting it as a good idea. It may lead people in a completely wrong direction.
     
    The only deployable packages I apply to DEV VMs are updates from Microsoft. If we have source code, it must be in source control, and when we get binaries from vendors, putting them to source control is the easiest way too. Even if we want to install them separately (e.g. I store them in Azure Artifacts feed), all we need it copying a few files, not wasting time with all the steps of deployable packages (such as the full build and synchronization).
     
     

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 664 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 522 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 303 User Group Leader

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans