Directory.Build.props

<Project>
    <!-- Import parent Directory.Build.props if it exists (e.g., when running as submodule of Pro) -->
    <Import Project="../Directory.Build.props" 
            Condition="Exists('$(MSBuildThisFileDirectory)../Directory.Build.props') AND '$(UseProjectReferences)' == 'true'"/>

    <PropertyGroup>
        <Nullable>enable</Nullable>
        <ImplicitUsings>enable</ImplicitUsings>
    </PropertyGroup>

    <!--
        By default, samples reference GeoBlazor NuGet packages with Version="*" (latest).
        Set UseProjectReferences=true and configure the paths below to use local project references instead.
        This is useful when developing GeoBlazor Core/Pro alongside the samples (e.g., as submodules).

        Example usage:
          dotnet build /p:UseProjectReferences=true /p:CoreProjectPath=../GeoBlazor/src/dymaptic.GeoBlazor.Core /p:ProProjectPath=../GeoBlazor.Pro/src/dymaptic.GeoBlazor.Pro
    -->
    <PropertyGroup Condition="'$(UseProjectReferences)' == 'true'">
        <CoreProjectPath Condition="'$(CoreProjectPath)' == ''">$(MSBuildThisFileDirectory)..\GeoBlazor\src\dymaptic.GeoBlazor.Core</CoreProjectPath>
        <ProProjectPath Condition="'$(ProProjectPath)' == ''">$(MSBuildThisFileDirectory)..\GeoBlazor.Pro\src\dymaptic.GeoBlazor.Pro</ProProjectPath>
        <ArtifactsPath>$(MSBuildThisFileDirectory).artifacts</ArtifactsPath>
        <!-- Source-ref sample hosts: drop the ESBuild-emitted Core/Pro JS from the MapStaticAssets endpoint manifest so
             they aren't fingerprinted/listed; UseStaticFiles still serves them at their _content path. Matched against
             the served route, which for RCL assets is _content/{PackageId}/... . Retain the framework default. -->
        <StaticWebAssetEndpointExclusionPattern>
            $(StaticWebAssetEndpointExclusionPattern);_content/dymaptic.GeoBlazor.Core/js/**;_content/dymaptic.GeoBlazor.Pro/js/**
        </StaticWebAssetEndpointExclusionPattern>
    </PropertyGroup>

</Project>