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) / How to move customizat...
Microsoft Dynamics AX (Archived)

How to move customizations from local VHD to the cloud?

(0) ShareShare
ReportReport
Posted on by Peter Samir 446

Dears,

We have Dynamics 365 for operations and according to our business needs we have to apply some customizations into forms.

We downloaded the development VHD into a local machine and also we have three environments that we got with the subscription (Build / Test / Production).

We started to set our customizations using the visual studio into the local machine. Now I need to apply these customizations to the cloud ( Build, Test then Production) so I would like to know how to move these customizations??

Can it be done through the deployable package or there is another way through the VSTS?

Please Advise

*This post is locked for comments

I have the same question (0)
  • Verified answer
    nmaenpaa Profile Picture
    nmaenpaa 101,166 Moderator on at

    You should connect your dev and build boxes to your VSTS project. Then you can just login to build environment, get latest changes, compile and create deployable package(s). Or you can create a build definition in VSTS: docs.microsoft.com/.../continuous-build-test-automation

    After you have created a deployable package, upload it to LCS Asset library and deploy it to test. After succesful test deployment you can mark your package as Release candidate in LCS. Then you can request a production deployment from Microsoft.

  • Suggested answer
    Martin Dráb Profile Picture
    Martin Dráb 239,069 Most Valuable Professional on at

    You don't want to manually install any code to the build server; it will handle everything by itself. You run a build, it downloads code from VSTS, builds it and gives you a deployable package that you can download and apply to other environments.

  • Peter Samir Profile Picture
    Peter Samir 446 on at

    Dears Thanks for replies but I have a misunderstand.

    Once we got the subscription of Dynamics 365 someone from Microsoft contact us for onboarding.

    We have three default environments that we got from Dynamics 365 Sub  (Develop and test / Standard acceptance test / Production).

    We planned to use these environments as follow (DEV / Test / Live) but while boarding Microsoft representative informed us that the development environment can hold one developer only.

    But we have a team of developers that is why he advised me to buy additional environment or host to Azure or download a local VHD. We decided to download the local VHD and the environment is working fine.

    He advised me to use the (Develop and test) environment as a build.

    So why I need a Build as I can extract deployable package from local VM to the Test (Cloud)?

    And how to connect the DEV and build boxes to my VSTS project?

  • Suggested answer
    nmaenpaa Profile Picture
    nmaenpaa 101,166 Moderator on at

    You want to create the deployable package in build environment because otherwise you can't be sure that all deployed code is in version control.

    When you deploy the build environment from the customer lcs project, select topology "Build and test" instead of "Develop and test". Now all necessary build tools are installed automatically.

    You connect the dev boxes to VSTS by setting up VSTS connection in Visual Studio.

    There is plenty of documentation about this in Dynamics Docs and other places.

  • Verified answer
    Martin Dráb Profile Picture
    Martin Dráb 239,069 Most Valuable Professional on at

    The automated build takes code developed by your whole team on several VMs, so you don't have to manually synchronize them to be able to create a package. It guarantees that all code comes from VSTS - if you have a local change, it could be unintentionally deployed to production if you created a package from your VM; this risk doesn't exists with a build server. You can always track which version was build, return to a specific build (e.g. to branch the application to develop a hotfix for production) and so on.

    The build also compiles the application for you, so you don't have to stop development just to make a build. It also means that you can run it very often, which means that you can find bugs sooner.

    Regarding VSTS setup, this might help you: Setting Up Version Control in Dynamics 365 for Operations with Visual Studio.

  • Peter Samir Profile Picture
    Peter Samir 446 on at

    Thanks for your replies

    I follow the "Deployment with continuous build and test automation" article and I delete the (Develop and test) environment then redeployed it as (Build and test) environment.

    The Build definition/Build agent are now created into the VSTS.

    Now I am trying to connect the local development machine to the VSTS project according to the attached link:

    1- We started opening the VSTS from VS then we go to source control explorer to add folders in the VSTS Root and mapped the source of files from Local server to VSTS Project.

    2- Then we checked in all the pending changes and found that the changes appeared automatically. After then, we tried to map the created folders (Meta files-Project folder) from Local file to Source control explorer of VSTS .

    The mapping action is done successfully and we set check in for the changes made but unfortunately, the contents of the folders created in VSTS are still empty.

  • Martin Dráb Profile Picture
    Martin Dráb 239,069 Most Valuable Professional on at

    I'm confused by your steps, because you mentioned mapping twice.

    In either case, mapping doesn't put any files to VSTS, that's done by adding them a checking them into VSTS. Mapping is related only to your local working copy.

  • Martin Dráb Profile Picture
    Martin Dráb 239,069 Most Valuable Professional on at

    By the way, I strongly recommend that you or somebody else from your team learn at least basics of TFS/VSTS. Trying to learn such a critical system by trial and error isn't the best strategy; you risk wasting a lot of time dealing with problems you don't understand, with suboptimal design decisions, you would likely miss some configurations options that may help you etc.

    For example, you can watch some courses on Microsoft Virtual Academy (aka.ms/mva).

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
Joris dG Profile Picture

Joris dG 5

#2
Andrew Jones a1x Profile Picture

Andrew Jones a1x 2

#3
GL-01081504-0 Profile Picture

GL-01081504-0 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans