SC4ModMigrationAssistant.csproj

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>WinExe</OutputType>
    <TargetFramework>net10.0-windows</TargetFramework>
    <UseWPF>true</UseWPF>
    <Nullable>enable</Nullable>
    <ImplicitUsings>enable</ImplicitUsings>
    <AssemblyName>SC4ModMigrationAssistant</AssemblyName>
    <RootNamespace>SC4ModMigrationAssistant</RootNamespace>
	<ApplicationIcon>Assets\SC4ModMigrationAssistant.ico</ApplicationIcon>
    <LangVersion>latest</LangVersion>
    <ApplicationTitle>SC4 Mod Migration Assistant</ApplicationTitle>

    <!--
      Explicit GC settings: Workstation GC (not Server GC, which allocates one heap per CPU
      core and can use significantly more peak memory) with background (concurrent)
      collection enabled. This matters for machines with only 4-8 GB of RAM, which is an
      explicit target for this application.
    -->
    <ServerGarbageCollection>false</ServerGarbageCollection>
    <ConcurrentGarbageCollection>true</ConcurrentGarbageCollection>
  </PropertyGroup>

  <ItemGroup>
    <!-- Used to read Catalog.db (the SC4 Prop Texture Catalog) once downloaded from GitHub. -->
    <PackageReference Include="Microsoft.Data.Sqlite" Version="9.0.0" />
    <!--
      Microsoft.Data.Sqlite currently pulls in SQLitePCLRaw.lib.e_sqlite3 2.1.11, which bundles
      a SQLite version affected by CVE-2025-6965 (NU1903 warning on build). Microsoft hasn't
      shipped a fix for this transitively yet, so the native SQLite build is pinned directly
      here to a patched version until they do. If "dotnet list package" (run with its
      vulnerable-packages flag) still flags this after an update, bump the version below to
      whatever is currently newest.
    -->
    <PackageReference Include="SQLitePCLRaw.lib.e_sqlite3" Version="3.50.3" />
  </ItemGroup>

</Project>