MCC badges awarded For April - June
Check out the latest community members who earned a Microsoft Dynamics 365 Community Contributors (MCC) badge. | View
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 and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
Ever since “CRM 2011” Microsoft has been pushing the message that we should have unmanaged solutions only in Development environments. That message is being emphasized even more as we walk into the new Power Platform era.Ideas have been raised that one day we might not be allowed to import unmanaged solutions to an environment that is not explicitly tagged for Development.
There is a clear ambition from the platform team to provide the tools and features we need to implement a really solid ALM story, including Visual Studio (and hopefully also VS Code) extensions with tight integration to Azure DevOps and our Common Data Service environments.We have already seen that they are opening up the Solution System for any component types without having to explicitly build “solution awareness” into the components themselves. The first new members of the solution family are of course Canvas Apps and Flows. And very recently a number of new implovements to the ALM and automation capabilities for the platform.
Unmanaged solutions have one valid use case – they are required when we are spinning up new development environments. And this one use case could very well be handled by AzDO (or other repository / automation systems) features for extracting development solutions from source environments, possibly even completely abstracting away the whole concept of unmanaged solutions by unpacking the artifacts under the hood into the structure of xml fragments we use to get useful versioning of our customizations.
Of course all features required to perform these actions must be exposed in the SDK, since the SDK is the one and only way to interact with the CDS backend. So technically it would still be possible to export the development solutions, if you just write the code to do it.
I hope we are going to see a semi-near future where the whole process of “export unmanaged, extract with Solution Packager, update the repository” are integrated features of the Power Platform and Azure DevOps.
There is no longer any need for the possibility to do manual (or automated!) export of unmanaged solutions.
This should of course come with an opt in policy. You can continue to deliver in a rogue partner shoot from the hip fashion, many customers love the idea of being “super agile” and accept they don’t really have control of their delivery cycles.
But if this proposed change would see the light of day, I sure would want to go on the opt-in path.
The post No more Export as Unmanaged appeared first on The Dynamics 365 Trenches.
Business Applications communities