Use `FunctionsPreservedDependencies` to resolve "Could not load file or assembly" errors

[bryanknox]

Use FunctionsPreservedDependencies instead of _FunctionsSkipCleanOutput to resolve "Could not load file or assembly" errors.

For some info about FunctionsPreservedDependencies, see: https://docs.microsoft.com/en-us/azure/azure-functions/functions-develop-vs#configure-your-build-output-settings

This approach is a possible means to address Issue: #27

[bryanknox]

I'm not sure I like FunctionsPreservedDependencies better than _FunctionsSkipCleanOutput.

• FunctionsPreservedDependencies is (minimally) documented.
• _FunctionsSkipCleanOutput is not documented, but was recommended before FunctionsPreservedDependencies became available in Microsoft.NET.Sdk.Functions 3.0.12.
• Hunting down the assembly names to list in FunctionsPreservedDependencies elements is time consuming, and will have to be updated as the assemblies used by the functions run-time or function app change.
  • I had to run tests on the SampleFunctionApp in multiple scenarios in order to discover the assembly names that needed FunctionsPreservedDependencies elements.

[bryanknox]

See my summary and guidance notes in my comment in #27

[bryanknox]

Closing this PR without changes. The issue is not something that is going to be fixed. And in-process functions will be retired with .NET 6 or 8.

See my blog post: _FunctionsSkipCleanOutput and FunctionsPreservedDependencies.

[SeanFeldman]

And in-process functions will be retired with .NET 6 or 8.

Not until .NET 9. Still supported with .NET 8.

[bryanknox]

To clarify , " .NET 8 to be the last LTS release to receive in-process model support in Azure Functions." That's from .NET on Azure Functions – August 2023 roadmap update

End of support for .NET 8 is November 10, 2026, as per .NET and .NET Core Support Policy