How exactly does DurableFunctionsMonitor.DotNetBackend package 'inject' itself into your Function App project?

[drdamour]

it's been on my list to understand how to package some functions for inclusion in other function apps, and wanted to pick your brain if i could.

re:

DurableFunctionsMonitor/durablefunctionsmonitor.dotnetbackend/durablefunctionsmonitor.dotnetbackend.targets

Line 6 in 93b60aa

<FunctionsInDependencies>true</FunctionsInDependencies>

Does this make functions scan ALL dependencies for functions, or just this assembly?

re:

DurableFunctionsMonitor/durablefunctionsmonitor.dotnetbackend/durablefunctionsmonitor.dotnetbackend.targets

Line 96 in 93b60aa

AfterTargets="_FunctionsPostPublish"

why is this second task needed? does the publish task recreate the functions.json or does it sometimes skip the postbuildtask on a publish?

re:

DurableFunctionsMonitor/durablefunctionsmonitor.dotnetbackend/durablefunctionsmonitor.dotnetbackend.targets

Line 13 in 93b60aa

<Content Include="$(MSBuildThisFileDirectory)\..\DfmStatics\**" LinkBase="DfmStatics\">

i'm very confused how the assets works... they obv get packages in the nuget

DurableFunctionsMonitor/durablefunctionsmonitor.dotnetbackend/durablefunctionsmonitor.dotnetbackend.csproj

Lines 33 to 36 in 93b60aa

	<ItemGroup>
	<Content Include="DfmStatics\**">
	<CopyToOutputDirectory>Always</CopyToOutputDirectory>
	</Content>

and i think this means that they get put in the output of my build

DurableFunctionsMonitor/durablefunctionsmonitor.dotnetbackend/durablefunctionsmonitor.dotnetbackend.csproj

Lines 33 to 36 in 93b60aa

	<ItemGroup>
	<Content Include="DfmStatics\**">
	<CopyToOutputDirectory>Always</CopyToOutputDirectory>
	</Content>

so does

DurableFunctionsMonitor/durablefunctionsmonitor.dotnetbackend/durablefunctionsmonitor.dotnetbackend.targets

Line 13 in 93b60aa

<Content Include="$(MSBuildThisFileDirectory)\..\DfmStatics\**" LinkBase="DfmStatics\">

pull them from my output dir?

[scale-tone]

FunctionsInDependencies
Does this make functions scan ALL dependencies for functions, or just this assembly?

That setting is project-wide, it's not tied to any particular assembly, so I assume it scans all dependencies.

why is this second task needed? does the publish task recreate the functions.json or does it sometimes skip the postbuildtask on a publish?

Publish outputs its artifacts into a separate folder ($(PublishDir)), and function.json files there appear to be fresh new. AFAIR, those files are produced by a separate post-build/post-publish task, not the build task itself. So DfMon needs to run FixDfmPrefixesInFunctionJsonAfterPublish on those files as well.

so does durablefunctionsmonitor.dotnetbackend.targets pull them from my output dir?

When you install a NuGet-package, only its binaries (more precisely, the binaries inside its lib folder) get automatically copied to your project. So DfMon's statics need to be copied from package to your project separately, and that's what line 13 does.

[scale-tone]

Hope that helps :)