dotnet-installer/TestAssets/TestProjects/docker-compose/docker-compose.dcproj

<Project Sdk="Microsoft.Docker.Sdk">
  <PropertyGroup Label="Globals">
    <ProjectVersion>2.0</ProjectVersion>
    <DockerTargetOS>Linux</DockerTargetOS>
    <DockerLaunchAction>LaunchBrowser</DockerLaunchAction>
    <DockerServiceUrl>http://localhost:{ServicePort}</DockerServiceUrl>
    <DockerServiceName>testwebapplication</DockerServiceName>
  </PropertyGroup>
  <ItemGroup>
    <None Include="docker-compose.yml" />
  </ItemGroup>
</Project>
remove xml declarations (#19339) 2024-04-07 06:53:48 +00:00			`<Project Sdk="Microsoft.Docker.Sdk">`
Adds Microsoft.Docker.Sdk to CLI This change is to add Sdk.props and Sdk.targets of Microsoft.Docker.Sdk into CLI. This unblocks the scenario where a VS solution contains a few .NET Core projects as well as a docker-compose.dcproj project and people want to build the solution from command line with .NET Core CLI. With the Sdk.props and Sdk.targets being present in CLI, building docker-compose.dcproj becomes no-op so it won't block building the other .NET Core projects. 2018-01-17 19:12:19 +00:00			`<PropertyGroup Label="Globals">`
			`<ProjectVersion>2.0</ProjectVersion>`
			`<DockerTargetOS>Linux</DockerTargetOS>`
			`<DockerLaunchAction>LaunchBrowser</DockerLaunchAction>`
			`<DockerServiceUrl>http://localhost:{ServicePort}</DockerServiceUrl>`
			`<DockerServiceName>testwebapplication</DockerServiceName>`
			`</PropertyGroup>`
			`<ItemGroup>`
			`<None Include="docker-compose.yml" />`
			`</ItemGroup>`
			`</Project>`