Browse Source

In .NET Core 2.1.200, WinSCPnet.csproj.nuget.g.targets is created in a correct location, so removing the hack from d49ae8072b0.

On the other hand this version issues warning about BaseIntermediateOutputPath. For VS build, we can fix it by adding Directory.Build.props with MSBuildProjectExtensionsPath.
But for command-line build, it does not work. There we simply fix it by using the default output paths.

Source commit: 03ea6eaafcc207b2709cac63c014634d44ca14a0
Martin Prikryl 7 years ago
parent
commit
d09b0af7f9
1 changed files with 1 additions and 3 deletions
  1. 1 3
      dotnet/WinSCPnet.csproj

+ 1 - 3
dotnet/WinSCPnet.csproj

@@ -4,9 +4,7 @@
     <TargetFrameworks>net40;netstandard2.0</TargetFrameworks>
     <GenerateAssemblyInfo>false</GenerateAssemblyInfo>
     <AllowUnsafeBlocks>true</AllowUnsafeBlocks>
-    <OutputPath>$(FINAL_PATH)\win32\$(Configuration)</OutputPath>
-    <IntermediateOutputPath>$(INTERM_PATH)\win32\$(Configuration)</IntermediateOutputPath>
-    <BaseIntermediateOutputPath>$(INTERM_PATH)\win32\$(Configuration)</BaseIntermediateOutputPath>
+    <OutputPath>bin\$(Configuration)</OutputPath>
   </PropertyGroup>
   <PropertyGroup Condition=" '$(TargetFramework)' == 'netstandard2.0'">
     <DefineConstants>NETSTANDARD</DefineConstants>