From 019c2c18af11f44c54255de277564947335c57ef Mon Sep 17 00:00:00 2001 From: Marc Schweigert Date: Thu, 13 Jun 2024 10:45:16 -0400 Subject: [PATCH] Update README.md AB#1 --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index cfc7065..977cc51 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,7 @@ # Sample Dataverse Solution showcasing using cdsproj as the driver of fusion development +DELETEME + Fusion development is a term often used to describe bringing together low code and code first (aka pro code) technologies together when developing applications. The [Microsoft Power Platform](https://learn.microsoft.com/power-platform/) has both low code and code first extensibility. You can learn more about code first extensibility using the [Microsoft Power Platform developer documentation](https://learn.microsoft.com/power-platform/developer/). The mechanism for implementing Application Lifecycle Management (ALM) in Power Platform is called a [Solution](https://learn.microsoft.com/power-platform/alm/solution-concepts-alm). While fusion development is an often overloaded term, the sample Solution in this repo aims to share a Hello World example of fusion development grounded in source control being the source of truth. The source code was produced using the [Power Platform CLI](https://learn.microsoft.com/power-platform/developer/cli/introduction). In source control based ALM, the build process is what typically builds the source code into a deployable artifact. In Power Platform ALM, the Solution is the deployable artifact. The Power Platform CLI has a number of commands through [pac solution](https://learn.microsoft.com/power-platform/developer/cli/reference/solution) that enable source control based ALM for solutions through the `*.cdsproj` file. When using a `*.cdsproj` to drive the building of a Solution, you can achieve the "fusing" of low code and code first elements of your Solution by simply running `dotnet build`. ## This sample contains the following