Possible issue with Web.Config

Describe the bug

In the API template, both the web and test project target <Project Sdk="Microsoft.NET.Sdk.Web"> this makes them both web projects in the eyes of dotnet. When I publish, I get a Web.Config like this:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <location path="." inheritInChildApplications="false">
    <system.webServer>
      <handlers>
        <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />
      </handlers>
      <aspNetCore processPath="dotnet" arguments=".\MyApp.IntegrationTest.dll" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" hostingModel="inprocess" />
    </system.webServer>
  </location>
</configuration>
<!--ProjectGuid: 57839160-3C89-4A5A-BC23-A78F39551C1E-->

Emphasis on: arguments=".\MyApp.IntegrationTest.dll"

To Reproduce

Create a template with integration tests, publish, check Web.Config, it might produce one like the above. It did for my anyway.

Project template

API

Possible Solutions

• Be more explicit about which project to publish in CAKE.
• <IsPackable>false</IsPackable> and <IsPublishable>false</IsPublishable>

[RehanSaeed]

• Adding <Project Sdk="Microsoft.NET.Sdk.Web"> to the integration tests is required as indicated in the docs.
• xUnit adds <IsPackable>false</IsPackable> for you https://github.com/xunit/xunit/issues/1520.

As far as publishing goes if you are running the Publish task in the cake script, I see your point. It’s currently publishing all projects in the solution. There are two ways to solve this problem:

1. In the cake scripts publish step, only publish projects in the /Source subdirectory.
2. Add <IsPublishable>false</IsPublishable> to the integration test.

I’m leaning towards the first one. Does that solve your issue or have I missed something?

[faviann]

It did fix the issue. Thanks! (Sorry for the late answer)