There are 'duplicate attribute' errors for .AssemblyInfo.cs file after deployment

[v-ruizh]

OS: Windows
Node.js: V10.15.0
Build Version: 20190402.1
Azure Functions Core Tools: V2.4.498

Repro Steps:

1. Create a C# project.
2. Create a new function with 'HTTP trigger' template and 'Function' level.
3. Deploy this C# project to Azure Function app.
4. Wait for 1 minute and click 'PROBLEMS' panel to check the logs.

Expect:
There is no error in 'PROBLEMS' panel.

Actual:
There are 'duplicate attribute' errors for .AssemblyInfo.cs file.

More Info:

1. This issue don't reproduce for JavaScript/TypeScript and Python project.
2. This issue also reproduces on Azure Function extension previous release build 0.16.0.

[ejizba]

This happens because there is an AssemblyInfo file in both the "Debug" and "Release" folder. Once dotnet/vscode-csharp#1694 is fixed, we should be able to leverage the files.exclude setting to hide the "obj" folder and any of its errors

[ejizba]

Filed a new issue on omnisharp: dotnet/vscode-csharp#3050

[behnood-eghbali]

Solution:
Before debugging, add the following lines to each of the *.csproj files within the <PropertyGroup> section:

    <GenerateAssemblyCompanyAttribute>false</GenerateAssemblyCompanyAttribute>
    <GenerateAssemblyConfigurationAttribute>false</GenerateAssemblyConfigurationAttribute>
    <GenerateAssemblyFileVersionAttribute>false</GenerateAssemblyFileVersionAttribute>
    <GenerateAssemblyInformationalVersionAttribute>false</GenerateAssemblyInformationalVersionAttribute>
    <GenerateAssemblyProductAttribute>false</GenerateAssemblyProductAttribute>
    <GenerateAssemblyTitleAttribute>false</GenerateAssemblyTitleAttribute>
    <GenerateAssemblyVersionAttribute>false</GenerateAssemblyVersionAttribute>
    <GenerateTargetFrameworkAttribute>false</GenerateTargetFrameworkAttribute>
    <GenerateAssemblyInfo>false</GenerateAssemblyInfo>

[MikePennington]

How is this still an issue two and a half years later? This is a bug that pretty much anyone using Microsoft's flagship programming language running on their flagship serverless technology will encounter.

[nturinski]

Hi @MikePennington

I understand your frustration, but unfortunately this is stemming from the OmniSharp extension.

We're tracking both of those issues, but unless we edit user's .csproj files manually to include the changes mentioned here: #1154 (comment), there is not much the Azure Functions extension team can do about it.