420b7529c6
Forcing a new build order. Seems to fix the issue. Since the issue was already intermittent (race condition?) it's difficult to be sure
42 lines
1.4 KiB
XML
42 lines
1.4 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<Project Sdk="Microsoft.NET.Sdk">
|
|
|
|
<PropertyGroup>
|
|
<OutputType>Exe</OutputType>
|
|
<TargetFramework>net5.0</TargetFramework>
|
|
|
|
<PublishTrimmed>true</PublishTrimmed>
|
|
<PublishReadyToRun>true</PublishReadyToRun>
|
|
<RuntimeIdentifier>win-x64</RuntimeIdentifier>
|
|
<AppendTargetFrameworkToOutputPath>false</AppendTargetFrameworkToOutputPath>
|
|
<AppendRuntimeIdentifierToOutputPath>false</AppendRuntimeIdentifierToOutputPath>
|
|
</PropertyGroup>
|
|
|
|
<!--
|
|
When LibationWinForms and LibationCli output to the same dir, LibationCli must build before LibationWinForms
|
|
|
|
VS > rt-clik solution > Project Build Order...
|
|
Dependencies [tab]
|
|
Projects: LibationWinForms
|
|
manually check LibationCli
|
|
-->
|
|
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|AnyCPU'">
|
|
<OutputPath>..\LibationWinForms\bin\Debug</OutputPath>
|
|
</PropertyGroup>
|
|
|
|
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|AnyCPU'">
|
|
<OutputPath>..\LibationWinForms\bin\Release</OutputPath>
|
|
</PropertyGroup>
|
|
|
|
<ItemGroup>
|
|
<PackageReference Include="CommandLineParser" Version="2.8.0" />
|
|
</ItemGroup>
|
|
|
|
<ItemGroup>
|
|
<ProjectReference Include="..\ApplicationServices\ApplicationServices.csproj" />
|
|
<ProjectReference Include="..\AppScaffolding\AppScaffolding.csproj" />
|
|
<ProjectReference Include="..\FileLiberator\FileLiberator.csproj" />
|
|
</ItemGroup>
|
|
|
|
</Project>
|