Build and package code-first components
Makers can use ALM Accelerator components to apply source control strategies with Azure DevOps, including fully automated builds and deployments, without needing intimate knowledge of downstream technologies or manual intervention by the maker, administrator, developer, or tester. You can switch quickly from developing to source-controlling solutions and, ultimately, push apps to other environments with as few interruptions to your work as possible.
With the ALM Accelerator, you can source-control your code-first components—plug-ins and PowerApps component framework (PCF) controls—build and run unit test cases, and transport them to downstream environments.
Recommended repository folder structure for code-first components
To build and deploy code-first components, we recommend you have a folder structure like the following example in your repository, where "CreatorKit" is the Dataverse solution name:
📁.vs
📂CreatorKit
📁PCF
📁Plugins
Set up a plug-in project
Run the pac plugin init command to generate a folder structure, as shown in the following image.
Add plug-in files to the folder structure.
If you have legacy plug-in projects, copy the project files to the new folder structure.
Set up PCF projects
No other steps are required to set up PCF projects. Add your PCF controls to the {solution name}\PCF folder.
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for