Skip to content

Latest commit

 

History

History
72 lines (47 loc) · 2.2 KB

File metadata and controls

72 lines (47 loc) · 2.2 KB

Developing

We are happy to collaborate with developers and contributors interested in enhancing Power Platform development processes. If you have feedback, suggestions, or would like to contribute, please feel free to submit issues or pull requests.

Updating dependencies

Some projects include Microsoft.PowerApps.MSBuild.* packages. The current version is defined in Direcotry.Build.props file and is shared across all projects. We currently lock to a specific version to ensure highest-level compatibility. Some projects reference the Tasks project, and in this case, the latest version is always used as well.

Local building and debugging

For developing and testing, you may use this repo which has a basic setup done.

Package project

Run the following terminal command in the folder Tasks:

dotnet pack --configuration Debug

Consuming project

Add nuget.config file to your Dataverse solution project folder:

<configuration>
  <packageSources>
    <!-- package source is additive -->
    <add key="LocalBuildTasks" value="/{REPOSITORY PATH}/src/Tasks/bin/Release/" />
  </packageSources>
</configuration>

Clear all cached packages:

Note that the command below is going to nuke your entire local package cache. It might be wiser to navigate to .nuget\packages\talxis.devkit.build.dataverse.tasks and delete only the contents of this folder. If you can't delete it because it is in use, execute dotnet build-server shutdown first.

dotnet nuget locals --clear all

You might need to clear the Nuget.org cache to see a recently published package:

dotnet nuget locals http-cache --clear

Rebuild the project:

dotnet build --no-incremental --force

Attaching debugger

In folder where you want to run dotnet build:

set MSBUILDDEBUGONSTART=1
dotnet build -bl /m:1

You will get a promp to attach debugger into a Visual Studio instance.

MSBuild logs

Build the target project with:

dotnet build -bl

The produced logs can be opened in MSBuild Log Viewer.