Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
For each developer, we have one dedicated VM for development, at some point of time, we would like to refresh all the Dev VM and ensure they are identical. (Developers sometime may accidently create an orphan model or objects).
As long as these orphan models or objects are not checked-in, there shouldn't be any concern. These are just sitting in DEV VM and won't get released/deployed to other environments. Getting latest code from version control itself takes care of same code/model/objects across environments except objects/code/model not checked-in. Is there any particular concern that you want to bring up?
If you go to Source Control Explorer and get the latest version, it'll download all missing changes from version control. If you want to be sure that you have no extra local objects, simply delete folders with your packages before getting the latest version. Just make sure you have no pending changes (check in or shelve your changes if you do).
Developers can create objects in their dev machines , you can not control that, as long as your required code is in source control and they are syncing their machines and not checking in unwanted objects in source control you should be good.
Just one more question onto this thread.
I have two folder "Metadata" and "Projects" under my DEV branch as screenshot below:
Do we normally check in (Upload) all the standard Microsoft code (e.g. Application Suite) into Metadata folder or only our new customisation is enough?
Just your packages.
Business Applications communities