The addition of ConfigurationManager 6.0 is a breaking change for Azure Function Apps 3

We are continuously addressing and improving the SDK, if possible, make sure the problem persist in the latest SDK version.

Describe the bug The dependency on System.Configuration.ConfigurationManager 6.0.0 introduced in the latest version of Azure.Cosmos (3.29.0) conflicts with the pinned version bundled with Azure Function App 3.

To Reproduce

1. Create a new Azure Function App on version 3 of the SDK
2. Install Azure.Cosmos 3.29.0
3. Try to use the dependency in any manner, such as initializing a client

Expected behavior The expected behavior is for the exception not to be thrown.

Actual behavior An exception such as the following is thrown when using the library:

Could not load file or assembly 'System.Configuration.ConfigurationManager, Version=6.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. 
The system cannot find the file specified.at Microsoft.Azure.Cosmos.DocumentClient.Initialize(Uri serviceEndpoint,ConnectionPolicy connectionPolicy,Nullable`1 desiredConsistencyLevel,HttpMessageHandler handler,ISessionContainer sessionContainer,Nullable`1 enableCpuMonitor,IStoreClientFactory storeClientFactory,TokenCredential tokenCredential)at Microsoft.Azure.Cosmos.DocumentClient..ctor

Environment summary SDK Version: 3.29.0 OS Version (e.g. Windows, Linux, MacOSX): MacOSX

Additional context Add any other context about the problem here (for example, complete stack traces or logs).

[shibayan]

@ealsur Yes, this problem occurred only with Azure Functions V3. Azure Functions V4 worked fine because the offending System.Configuration.ConfigurationManager was not removed by the optimization process at publish time, but was left behind.

[shibayan]

This is due to the version 6.0.0 update of System.Configuration.ConfigurationManager package from Cosmos DB SDK v3.29 and the assembly optimization process in Azure Functions.

You may need to add _FunctionsSkipCleanOutput or FunctionsPreservedDependencies to csproj to resolve this.

  <PropertyGroup>
    <TargetFramework>netcoreapp3.1</TargetFramework>
    <AzureFunctionsVersion>v3</AzureFunctionsVersion>
    <_FunctionsSkipCleanOutput>true</_FunctionsSkipCleanOutput>
  </PropertyGroup>

or

  <ItemGroup>
    <FunctionsPreservedDependencies Include="System.Configuration.ConfigurationManager.dll" />
  </ItemGroup>