PL400 : Implement source control for projects including solutions and code assets (Implement application lifecycle management (ALM))

In the modern development world, version control systems are essential tools. Every software companies follow best practices and tools during the development process. Source control tools such as Git, GitHub and Azure DevOps and others are designed with the aim of improving the communication and software quality. Version control, also known as source control, is the practice of tracking and managing changes to software code. Version control systems are software tools that help software teams manage changes to source code over time.



A version control system serves the following purpose:
  • A version control enables multiple people to work together as a project.
  • Version control integrates the work done by different team members together.
  • Version control provides access to the historical version of our project.
In Power Platform and Dynamics 365 CE, solutions play an important role in shipping changes to developers across different environments. Deployment and source control are not the same in Power Platform as other software development processes. As such, if two different developers work in the same component, it is difficult to merge the entire component easily or with the help of any tool. Even Microsoft suggests a different approach to version control in Power Platform and Dynamics 365 CE.

As Microsoft's doc:

Microsoft Power Platform uses the solution feature of Microsoft Dataverse to track and manage apps, flows, tables, and even developer code components like JavaScript and plug-ins. Solutions are containers that can be used the transport project assets from one environment to another.
Solutions are a core part of Microsoft Power Platform application lifecycle management (ALM) strategy
As the best practice, Unmanaged Solution uses for development. A tool named SolutionPackager can be used to prepare solutions to be checked in.

SolutionPackager tool:

Solutions exported from a Dataverse environment are simply a compressed zip file with the metadata included. As a single binary file, it is not very effective or useful when placed into a source control repository.  The SolutionPackager tool is distributed as part of the NuGet package  Microsoft.CrmSdk.CoreTools. It can unpack a Dataverse solution into a series of XML files and other files so that these files can be easily managed by a source control system. SolutionPackager can also repack the solution zip file using the extracted components.

The SolutionPackager tool is an executable that you can use to conduct the following actions:
  1. Extract: Extract solution .zip file to a folder
  2. Pack: Pack a folder into a .zip file
Version Control and Build Management:
  1. Solution are unpacked using the solution package and version control in a repository such Team foundation or GitHub.
  2. Solutions are built through an automated process that invokes the solution packages to repack the solution into solution.zip file.
  3. Packages are built through an automated process that combines the required solutions and configuration deployer.zip file.
Conclusion:

As per the documentation the unmanaged solution is used in the development environment while we make changes to our application. We can export our unmanaged solutions and unpack them, so that we will have a copy of our unmanaged solution source in our repository.

Comments

Post a Comment

Popular posts from this blog

PCF vs. Web Resources: Choosing the Right Extensibility Tool for Dataverse

Image
Extensibility refers to the ability to be extended or augmented beyond the default capabilities of the platform. This involves customization but also includes more advanced techniques, such as coding, integration with external services, and the use of custom components. In the context of Power Platform and Dynamics CRM, the term "extend behavior" refers to the ability to customize and extend the functionality of the platform to meet specific business needs. Extensibility often requires technical skills, such as coding in JavaScript, C#, or using tools like Azure Logic Apps and Power Automate for complex integrations. Customization  is a subset of extensibility. Customization involves configuring and modifying existing elements within the platform to suit specific business needs. Extensibility, on the other hand, covers a wide range of functions and techniques, including customization and more advanced development and integration tasks, to extend the capabilities of the Power
Read more

Is Debt Prosperity or Trap?

 “What can be added to the happiness of a man who is in health, out of debt, and has a clear conscience?”  Adam Smith Grandfather Bhishma lay on the bed of arrows and was preaching the future king of Hastinapur about political science, economics and the duties of the king. He took a deep breath and told Yudhishthira " Fire, debt and enemies must be dealt with quickly and completely. If there is any balance left, they can continue to grow. " The future king was listening with curiosity and was eager to learn about the complete knowledge from his grandsire. Each moment was important as the sun was moving from south to north. Either we read the quote of the father of modern economics or both ancient great scholars are advising to avoid debt. But the whole of modern economics is based on the debt that advises the public to borrow money. The aggressive campaign of banks and financial institutions has been luring more and more loans. Even democratic governments and public banks con
Read more

Exam PL-400: Microsoft Power Platform Developer

 Create a technical design (10-15%) Validate requirements and design technical architecture design and validate the technical architecture for a solution design authentication and authorization strategy determine whether you can meet requirements with out-of-the-box functionality determine when to use Logic Apps versus Power Automate flows determine when to use serverless computing, plug-ins, or Power Automate determine when to build a virtual entity data source provider and when to use connectors Design solution components design a data model design Power Apps reusable components design custom connectors design server-side components Describe Microsoft Power Platform extensibility points describe Power Virtual Agents extensibility points including Bot Framework skills and Power Automate flows describe Power BI extensibility points including Power BI APIs, custom visuals, and embedding Power BI apps in websites and other applications describe Power Apps portal extensibility points incl
Read more