Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
​Application Lifecycle Management on Microsoft Power Platform

You're reading from   ​Application Lifecycle Management on Microsoft Power Platform A comprehensive guide to managing the deployment of your solutions

Arrow left icon
Product type Paperback
Published in Oct 2024
Publisher Packt
ISBN-13 9781835462324
Length 222 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
Benedikt Bergmann Benedikt Bergmann
Author Profile Icon Benedikt Bergmann
Benedikt Bergmann
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Preface 1. Chapter 1: An Intro to ALM 2. Chapter 2: ALM in Power Platform FREE CHAPTER 3. Chapter 3: Power Platform Environments 4. Chapter 4: Dataverse Solutions 5. Chapter 5: Power Platform CLI 6. Chapter 6: Environment Variables, Connection References, and Data 7. Chapter 7: Approaches to Managing Changes in Power Platform ALM 8. Chapter 8: Essential ALM Tooling for Power Platform 9. Chapter 9: Project Setup 10. Chapter 10: Pipelines 11. Chapter 11: Advanced Techniques 12. Chapter 12: Continuous Integration/Continuous Delivery 13. Chapter 13: Deepening ALM Knowledge 14. Assessments 15. Index 16. Other Books You May Enjoy

Folder structure

This section will give you an overview of how a folder structure in your repository might look to help you structure your Power Platform development. Note that this is not the only possibility; there are many right answers to this question. This section only shows one possible solution. The setup is also intended for having a mono repo. This means one repository holding all the code for your implementation. If you use separate repos for separate parts of your project (Azure Functions in one repo, Dataverse plugins in another, configuration in another still, and so on), this structure might not suit your needs. In addition, the pipelines will get more complex.

Root folder

In the root folder, you could have the following:

  • Development: This folder would contain all your actual development. For example, it might contain plugins, TypeScript, or surrounding applications such as Azure Functions or APIs.
  • PipelineDefinition: As the name suggests, this folder...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime