Directory.Build.props

<?xml version="1.0" encoding="utf-8"?>
<Project>

  <PropertyGroup Condition="Exists('$(MsBuildThisFileDirectory)..\version.json')">
    <InPrivateRepo>true</InPrivateRepo>
    <PackageOutputPath>$(MSBuildThisFileDirectory)..\bin\packages\</PackageOutputPath>
  </PropertyGroup>

  <PropertyGroup>
    <PackageOutputPath Condition="'$(PackageOutputPath)' == ''">$(MsBuildThisFileDirectory)build\packages\</PackageOutputPath>
    <OutputPath>bin\$(Configuration)\</OutputPath>
    <SatelliteResourceLanguages>en-US</SatelliteResourceLanguages>
    <NoWarn>$(NoWarn)1591;</NoWarn>
    <GenerateDocumentationFile>true</GenerateDocumentationFile>
    <!-- Create the nupks as well so we can use them right away -->
    <GeneratePackageOnBuild>$(BuildingInsideVisualStudio)</GeneratePackageOnBuild>
    <!-- Use stable nuspec file name during development -->
    <!-- It leads to for example VL.CoreLib\src\obj\VL.CoreLib.nuspec which our package loader can pick up to infer the exact package version -->
    <!-- Combined with the GeneratePackageOnBuild this allows to reference this project as a package in C# project references from within VL files -->
    <OutputFileNamesWithoutVersion Condition="'$(OutputFileNamesWithoutVersion)' == ''">true</OutputFileNamesWithoutVersion>
    <NuspecOutputPath>obj\</NuspecOutputPath>
    <!-- Maybe interesting, see nuget pack command line docs -->
    <!--<InstallPackageToOutputPath>true</InstallPackageToOutputPath>-->

    <!-- Must be turned off or publishing from inside VS fails -->
    <AppendRuntimeIdentifierToOutputPath>false</AppendRuntimeIdentifierToOutputPath>

    <!-- Enable central package version feature https://devblogs.microsoft.com/nuget/introducing-central-package-management/ -->
    <ManagePackageVersionsCentrally>true</ManagePackageVersionsCentrally>
    <!-- This flag causes the generated nuget to take dependencies on all transitive packages and would therefor blow up our zip file (InstallPackages target in Build.cs) -->
    <!--<CentralPackageTransitivePinningEnabled>true</CentralPackageTransitivePinningEnabled>-->
    
    <!-- Package properties -->
    <Year>$([System.DateTime]::Now.ToString('yyyy'))</Year>
    <IncludeFrameworkReferencesInPackage>false</IncludeFrameworkReferencesInPackage>
    <Authors>vvvv group</Authors>
    <Owners>$(Authors)</Owners>
    <Copyright>Copyright © $(Year) by $(Authors). All rights reserved.</Copyright>
    <PackageProjectUrl>http://vvvv.org</PackageProjectUrl>
    <Product>vvvv</Product>
    <PackageIcon>nugeticon.png</PackageIcon>

    <!-- Gets overwritten by Nerdbank.GitVersioning (if present). Otherwise it's a good default to avoid assembly manifest load issues. -->
    <!-- We should be able to get rid of this once VL.StandardLibs has its own release cycle. -->
    <Version>2024.6.4</Version>
  </PropertyGroup>

  <!-- Read the version information from our private repo (for now) -->
  <PropertyGroup Condition="'$(InPrivateRepo)' == 'true'">
    <GitRepoRoot>$(MSBuildThisFileDirectory)..\</GitRepoRoot>
    <!-- https://github.com/dotnet/Nerdbank.GitVersioning/blob/master/doc/msbuild.md -->
    <GitVersionBaseDirectory>$(MSBuildThisFileDirectory)..\</GitVersionBaseDirectory>
  </PropertyGroup>

  <ItemGroup Condition="'$(InPrivateRepo)' == 'true'">
    <PackageReference Include="Nerdbank.GitVersioning">
      <PrivateAssets>all</PrivateAssets>
      <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets>
    </PackageReference>
  </ItemGroup>

  <!-- Disable pdb files in Release builds -->
  <PropertyGroup Condition="'$(Configuration)' == 'Release'">
    <DebugSymbols>false</DebugSymbols>
    <DebugType>None</DebugType>
    <AllowedReferenceRelatedFileExtensions>.xml</AllowedReferenceRelatedFileExtensions>
  </PropertyGroup>
  
</Project>