add a build action

[FH-Inway]

This adds a build action based on FSC-PS for GitHub.

The build action can be triggered manually. It is also triggered when a pull request gets created or changes are made to an existing one. Here is an example from my fork on what the pull request build would look like: https://github.com/FH-Inway/D365FOAdminToolkit/actions/runs/7775675807

Couple of notes:

• The .json files added are part of the FSC-PS framework. The most relevant is probably .FSC-PS/settings.json, which has the buildVersion setting that defines on what version of the D365FO NuGet packages the build is run.
• The actual build action is defined by .github/workflows/build.yml. This started out as a copy of https://github.com/ciellosinc/FSC-PS.FSC/blob/main/.github/workflows/build.yml, to which I made several changes. The most substantial ones are:
  • adding a build step for the .NET project. The resulting assemblies are copied to the D365FO build step to the Metadata bin folder to enable the build for the D365FOAdminToolkit module
  • this .NET build step required adding a new action to https://github.com/ciellosinc/FSC-PS-Actions so that the D365FO NuGet packages could be restored outside of the RunPipeline action. This action currently lives on my fork, but I'm hoping to get it added to the FSC-PS-Actions repo.
  • the changes in the D365FOAdminToolkitNET.csproj file are to enable both local development as well as the build in the build action. This is done by dynamically providing references to the Microsoft.Dynamics.AX assemblies based on whether the AOSService folder or the packages folder with the D365FO NuGets contents exists.

[FH-Inway]

@ameyer505 Thanks for the merge, seems the action now finally ran. Did you have to approve something first? It seems the action was triggered yesterday by #13 , but only started today.

[ameyer505]

@FH-Inway I did two separate PR's to the dev branch yesterday and neither immediately kicked off the build but you are correct it looks like the last one actually 'triggered' it. Not sure why there was a delay between the PR and the build though.

[FH-Inway]

@ameyer505 The other PR was #12 which was my pr that added that action. Only actions that "live" on the default branch are triggered, so it makes sense that only the pr after mine triggered it. Let's wait for the next pr to see if it triggers and runs the action directly or if there is another delay.