Different behaviour of paket vs. nuget in context of contentfiles

Hi guys

Working with Azure function projects using paket is actually quite hard. Updating packages in our solution gives me massive headache last days. The reason is, that Microsoft added a dependency to WebJobs.Sources to WebJobs.Extensions.ServiceBus that conflicts with our stylecop policy.
I was not able to prevent paket from including this files in my project. Even nuget Microsoft.Azure.WebJobs.Sources content: none does not help.
Maybe somebody has an idea how to deal with that.

Cheers Thomy

Description

Different behaviour of C# project when using nuget and paket in context of Azure Function using ServiceBus.

Issue

Using ServiceBus-Bindings requires adding the package Microsoft.Azure.WebJobs.Extensions.ServiceBus to the project. Version 4.1.2 (at this time) has a dependency to Microsoft.Azure.WebJobs.Sources that adds 10 C# source code files as content-files to the referencing solution.
Having Stylecop active with TreatWarningsAsErrors=true results in build failures.

Repro steps

Demo project: https://github.com/thomas-mutter/azure-servicebus-test/
Branches: paket-version, nuget-version

Expected behavior

When using paket, subdependencies should not include content-files.

Actual behavior

Actually I was not able to exclude content-files from this source-package from the solution.

Known workarounds

Adopt stylecop-rules to accept code style coming from source files.

Start with the linked demo project and compare the paket-version and nuget-version branches for Microsoft.Azure.WebJobs.Extensions.ServiceBus. Trace how the Microsoft.Azure.WebJobs.Sources content files are included, then verify that the expected Paket behavior is demonstrated without those files being added to the project.