I had this strange situation today, for which I cannot find a solution.
Our setup is the following:
- 2 developers are working on their own virtual machines running Dynamics For Operations and Finance Update 8, we use VSTS for source control.
- A development/build machine hosted on azure, where we build our releases.
- We then apply those releases/deployable packages to other environments.
How I created my deployable package
- did a "get latest version" for all the objects in my package, on the dev machine in the source control explorer
- Then I used the Dynamics 365 > "build models" function in Visual studio, and choose to build all the referenced packages.
- Then I uploaded the deployable package to LCS and applied it to my destination environment.
What is the problem
Today it appeared that all new objects were not in this destination environment, extensions on existing standard tables were in the package.
I did notice the following however:
When building each visual studio solution, there were binary files added to the folder C:\AOSService\PackagesLocalDirectory\<Mypackage<\bin
But then when creating a depoyable package, the complete model is built, and serveral 'netmodulefiles' and others were deleted again.
I can even see those files become a '.delete' file when the model build is running.
What's going on here?
Your help is greatly appreciated
Kind regards
Mathieu
