### Configure Debugger Start Program (SonetaAddonStartProgram)

Source: https://context7.com/soneta/soneta.msbuild.sdk/llms.txt

The SDK automatically detects the latest enova365 installation and sets `SonetaExplorer.exe` as the debugger start program with the correct extension path. You can override the default start program path by setting `<SonetaAddonStartProgram>` to your desired executable. To disable the automatic start mechanism, leave `<SonetaAddonStartProgram>` empty.

```xml
<!-- Automatyczne wykrycie — brak konfiguracji wymagana -->
<!-- SDK wykona odpowiednik: -->
<!-- StartProgram = C:\Program Files (x86)\Soneta\enova365 2510.0.0\SonetaExplorer.exe -->
<!-- StartArguments = --extpath=C:\Projekty\MojDodatek\bin\debug\net6.0\ -->

<!-- Nadpisanie ścieżki programu startowego (opcjonalne): -->
<PropertyGroup>
  <SonetaAddonStartProgram>D:\enova365\enova365 2510.0.0\SonetaExplorer.exe</SonetaAddonStartProgram>
</PropertyGroup>

<!-- Wyłączenie mechanizmu automatycznego startu: -->
<PropertyGroup>
  <SonetaAddonStartProgram></SonetaAddonStartProgram>
</PropertyGroup>
```

--------------------------------

### Import Soneta.MsBuild.SDK into a Project

Source: https://context7.com/soneta/soneta.msbuild.sdk/llms.txt

Specify the SDK in your .csproj file to automatically configure the project. MSBuild will download the package and set up references.

```xml
<!-- MojDodatek/MojDodatek.csproj -->
<?xml version="1.0" encoding="utf-8"?>
<Project Sdk="Soneta.Sdk/1.1.7">
  <PropertyGroup>
    <TargetFramework>$(SonetaTargetFramework)</TargetFramework>
  </PropertyGroup>
</Project>
```

--------------------------------

### Test Local SDK Package Before Publishing

Source: https://context7.com/soneta/soneta.msbuild.sdk/llms.txt

Build the SDK package, push it to a local NuGet feed, and update `global.json` to point to the local version for testing.

```powershell
# 1. Zbuduj projekt SDK
dotnet build src/Soneta.Sdk/Soneta.Sdk.csproj -c Release

# 2. Wypchnij paczkę do lokalnego folderu z paczkami
cd src/Soneta.Sdk/bin/Release
dotnet nuget push Soneta.Sdk.1.1.7.nupkg -s C:\Users\<nazwaużytkownika>\.nuget\packages

# 3. W global.json projektu docelowego wskaż wersję lokalną
# {
#   "msbuild-sdks": { "Soneta.Sdk": "1.1.7" }
# }
# SDK będzie teraz widoczne dla nowych projektów w danym środowisku.
```

--------------------------------

### Push NuGet Package to Local Feed

Source: https://github.com/soneta/soneta.msbuild.sdk/blob/develop/README.md

After building the SDK, use this command to push the generated .nupkg file to your local NuGet package repository. This makes the SDK available for new projects.

```powershell
dotnet nuget push nazwaPaczki.nupkg -s C:\Users....nuget\packages
```

--------------------------------

### Configure Assembly Search Paths

Source: https://github.com/soneta/soneta.msbuild.sdk/blob/develop/README.md

Configure the ReferencePath and AssemblySearchPaths properties in your project file to specify a directory where the SDK should look for referenced libraries. This avoids the need for individual HintPath entries for multiple DLLs.

```xml
<PropertyGroup>
  <ReferencePath>C:\Program Files (x86)\Soneta\enova365 1908.0.1.17324\</ReferencePath>
  <AssemblySearchPaths>$(AssemblySearchPaths);$(ReferencePath);</AssemblySearchPaths>
</PropertyGroup>
```

--------------------------------

### Configure Soneta Library Versions with Directory.Build.props

Source: https://context7.com/soneta/soneta.msbuild.sdk/llms.txt

Use `Directory.Build.props` to set the Soneta libraries version (`SonetaPackageVersion`) and .NET platform version (`SonetaTargetFramework`) for the entire solution. The SDK uses these settings to select appropriate NuGet packages.

```xml
<!-- Directory.Build.props (obok pliku *.sln) -->
<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="14.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <PropertyGroup>
    <!-- Wersja bibliotek Soneta (paczka Soneta.Products.Modules / Soneta.Products.Test) -->
    <SonetaPackageVersion>2510.0.0</SonetaPackageVersion>
    <!-- Docelowa wersja .NET -->
    <SonetaTargetFramework>net6.0</SonetaTargetFramework>
    <!-- Opcjonalnie: własne zmienne wielokrotnego użytku -->
    <MojaWersjaKomponentu>3.2.1</MojaWersjaKomponentu>
  </PropertyGroup>
</Project>
```

--------------------------------

### Automatic File Type Handling (common.items.props)

Source: https://context7.com/soneta/soneta.msbuild.sdk/llms.txt

The `common.items.props` file automatically registers numerous file patterns as `EmbeddedResource` without manual `.csproj` edits. Files like `*.business.xml` are automatically marked for packaging into NuGet. No explicit additions to `.csproj` are needed as files are detected via globs.

```xml
<!-- Pliki obsługiwane automatycznie jako EmbeddedResource: -->
<!--
  *.config.xml, *.convert.sql, *.dbinit.xml
  *.*form.xml, *.*form.mobile.xml, *.*form.console.xml
  *.*form.browsernew.xml, *.*form.premium.xml, *.*form.standard.xml
  *.rightstree.xml, *.role.xml, *.publish.xml
  *.repx, *.repx.cs, *.snippet.cs
  *.dotx (szablony Word)
  Repx\*.jpg, Repx\*.gif, Repx\*.png, Repx\*.bmp
  Properties\licenses.licx*
-->

<!-- *.business.xml jest automatycznie oznaczany jako Pack=true i trafia do paczki NuGet:
     PackagePath="schema/modul.business.xml" -->

<!-- Nie trzeba nic dopisywać do *.csproj — pliki są wykrywane automatycznie przez globy -->
```

--------------------------------

### Manually Reference Single Library via HintPath

Source: https://context7.com/soneta/soneta.msbuild.sdk/llms.txt

Add a reference to a single library using `HintPath` when it's not automatically provided by the SDK. Ensure `SpecificVersion` and `Private` are set appropriately.

```xml
<ItemGroup>
  <Reference Include="Soneta.Forms">
    <HintPath>C:\Program Files (x86)\Soneta\enova365 2510.0.0\Soneta.Forms.dll</HintPath>
    <SpecificVersion>false</SpecificVersion>
    <Private>false</Private>
  </Reference>
</ItemGroup>
```

--------------------------------

### Add Direct DLL Reference to Project

Source: https://github.com/soneta/soneta.msbuild.sdk/blob/develop/README.md

Use this snippet to add a direct reference to a specific DLL file within your .csproj file. Ensure the HintPath points to the correct location of the DLL.

```xml
<ItemGroup>
  <Reference Include="Soneta.Forms">
    <HintPath>C:\Program Files (x86)\Soneta\enova365 1908.0.1.17324\Soneta.Forms.dll</HintPath>
    <SpecificVersion>false</SpecificVersion>
    <Private>false</Private>
  </Reference>
</ItemGroup>
```

--------------------------------

### Create and Push Release Tag

Source: https://github.com/soneta/soneta.msbuild.sdk/blob/develop/RELEASING.md

Create an annotated tag for the release version at the current master branch point and push all tags to the remote repository.

```bash
git tag -a vx.y.z origin/master
git push origin --tags
```

--------------------------------

### Automatic References for UI Projects

Source: https://context7.com/soneta/soneta.msbuild.sdk/llms.txt

UI projects, identified by names ending in '.UI', automatically receive `Soneta.Products.Modules` and `System.ValueTuple` NuGet packages.

```xml
<!-- Projekt UI kończący się na .UI -->
<!-- MojDodatek.UI/MojDodatek.UI.csproj -->
<?xml version="1.0" encoding="utf-8"?>
<Project Sdk="Soneta.Sdk">
  <PropertyGroup>
    <TargetFramework>$(SonetaTargetFramework)</TargetFramework>
  </PropertyGroup>
</Project>
<!-- SDK automatycznie doda: Soneta.Products.Modules, System.ValueTuple -->
```

--------------------------------

### Centralize SDK Version with global.json

Source: https://context7.com/soneta/soneta.msbuild.sdk/llms.txt

Define the SDK version in a single `global.json` file for multiple projects in a solution. This avoids specifying the version in each .csproj file.

```json
// global.json (obok pliku *.sln)
{
  "msbuild-sdks": {
    "Soneta.Sdk": "1.1.7"
  }
}
```

```xml
<!-- MojDodatek/MojDodatek.csproj — bez numeru wersji -->
<?xml version="1.0" encoding="utf-8"?>
<Project Sdk="Soneta.Sdk">
  <PropertyGroup>
    <TargetFramework>$(SonetaTargetFramework)</TargetFramework>
  </PropertyGroup>
</Project>
```

--------------------------------

### Commit and Push Prerelease Version to Develop

Source: https://github.com/soneta/soneta.msbuild.sdk/blob/develop/RELEASING.md

After tagging the release, update the version on the develop branch to a prerelease format and commit these changes. Push the updated develop branch.

```bash
git commit -m "Wersja następna: x.y.z+1-prerelease"
git push origin develop
```

--------------------------------

### Reference Entire Library Folder via ReferencePath

Source: https://context7.com/soneta/soneta.msbuild.sdk/llms.txt

Set `ReferencePath` to include an entire folder of libraries and add it to `AssemblySearchPaths`. This is useful for managing multiple libraries.

```xml
<PropertyGroup>
  <ReferencePath>C:\Program Files (x86)\Soneta\enova365 2510.0.0\</ReferencePath>
  <AssemblySearchPaths>$(AssemblySearchPaths);$(ReferencePath);</AssemblySearchPaths>
</PropertyGroup>
```

--------------------------------

### Configure Project Output Aggregation (AggregateOutput / AggregatePath)

Source: https://context7.com/soneta/soneta.msbuild.sdk/llms.txt

Control where build outputs are placed. By default, outputs are aggregated to `../bin/`. Use `AggregatePath` to specify a custom location or set `AggregateOutput` to `false` to disable aggregation for a specific project.

```xml
<!-- Directory.Build.props lub konkretny *.csproj -->
<PropertyGroup>
  <!-- Domyślnie true — wszystkie projekty budują do ..\bin\ -->
  <AggregateOutput>true</AggregateOutput>

  <!-- Własna ścieżka agregacji (relatywna lub bezwzględna) -->
  <AggregatePath>..\dist\</AggregatePath>

  <!-- Lub wyłączenie agregacji dla konkretnego projektu -->
  <!-- <AggregateOutput>false</AggregateOutput> -->
</PropertyGroup>

<!-- Rezultat (przy domyślnych ustawieniach):
     ..\bin\debug\net6.0\MojDodatek.dll
     ..\bin\debug\net6.0\MojDodatek.UI.dll   -->
```

--------------------------------

### Commit and Push Next Version to Develop

Source: https://github.com/soneta/soneta.msbuild.sdk/blob/develop/RELEASING.md

Commit changes for the next version to the develop branch and push them. This is done before merging to master.

```bash
git commit -m "Wersja następna: x.y.z"
git push origin develop
```

--------------------------------

### Configure SDK Update Check Interval

Source: https://context7.com/soneta/soneta.msbuild.sdk/llms.txt

Configure the interval for checking new SDK versions. Set `SonetaSdkUpdateIntervalTime` to 'None' to disable checks. Default is disabled.

```xml
<PropertyGroup>
  <!-- Jednostki: Seconds, Minutes, Hours, Days, Weeks, Months, Years -->
  <!-- Domyślnie 'None' — sprawdzanie wyłączone -->
  <SonetaSdkUpdateIntervalTime>Days</SonetaSdkUpdateIntervalTime>
  <SonetaSdkUpdateIntervalValue>1</SonetaSdkUpdateIntervalValue>
</PropertyGroup>
```

--------------------------------

### Merge Develop into Master and Push

Source: https://github.com/soneta/soneta.msbuild.sdk/blob/develop/RELEASING.md

Integrate the develop branch into the master branch and push the changes to the remote repository. This prepares for a release from master.

```bash
git checkout master
git merge develop
git push origin master
```

--------------------------------

### Automatic References for Test Projects

Source: https://context7.com/soneta/soneta.msbuild.sdk/llms.txt

Test projects, identified by names containing 'Test' or by the `<IsTestProject>true</IsTestProject>` flag, automatically receive NUnit, NSubstitute, and AwesomeAssertions NuGet packages.

```xml
<!-- Projekt testowy — wystarczy sama nazwa zawierająca "Test" -->
<!-- MojDodatek.Test/MojDodatek.Test.csproj -->
<?xml version="1.0" encoding="utf-8"?>
<Project Sdk="Soneta.Sdk">
  <PropertyGroup>
    <TargetFramework>$(SonetaTargetFramework)</TargetFramework>
    <!-- Można jawnie ustawić flagę, jeśli nazwa nie zawiera "Test" -->
    <!-- <IsTestProject>true</IsTestProject> -->
  </PropertyGroup>
</Project>
<!-- SDK automatycznie doda:
     NUnit, Soneta.Products.Test, NUnit3TestAdapter,
     Microsoft.NET.Test.Sdk -->
```

--------------------------------

### Enable Automatic Code Generator Execution (ExecuteSonetaGenerator)

Source: https://context7.com/soneta/soneta.msbuild.sdk/llms.txt

The `ExecuteSonetaGenerator` target automatically converts `*.business.xml` or `*.config.xml` files to `.cs` files before compilation. No additional configuration is needed in the `.csproj` file if the generator should run. To disable it for a specific project, set `RunSonetaGenerator` to `false`.

```xml
<!-- Struktura projektu z plikami XML do wygenerowania -->
<!--
MojDodatek/
├── MojDodatek.csproj
├── Modul/
│   ├── modul.business.xml      ← wejście generatora
│   └── modul.config.xml        ← wejście generatora
└── ...
-->

<!-- MojDodatek.csproj — żadna dodatkowa konfiguracja nie jest wymagana -->
<?xml version="1.0" encoding="utf-8"?>
<Project Sdk="Soneta.Sdk">
  <PropertyGroup>
    <TargetFramework>$(SonetaTargetFramework)</TargetFramework>
  </PropertyGroup>
</Project>

<!-- Po kompilacji SDK automatycznie wygeneruje:
     Modul/modul.business.cs  (AutoGen=True, DependentUpon=modul.business.xml)
     Modul/modul.config.cs    (AutoGen=True, DependentUpon=modul.config.xml) -->

<!-- Aby wyłączyć generator dla konkretnego projektu: -->
<PropertyGroup>
  <RunSonetaGenerator>false</RunSonetaGenerator>
</PropertyGroup>
```

--------------------------------

### Disable Default Soneta Package References

Source: https://context7.com/soneta/soneta.msbuild.sdk/llms.txt

Set `EnableDefaultSonetaPackageReferences` to `false` to disable automatic package inclusion by the SDK. This is useful for manual dependency management.

```xml
<PropertyGroup>
  <!-- Wyłącza automatyczne dołączanie Soneta.Products.Modules, NUnit itp. -->
  <EnableDefaultSonetaPackageReferences>false</EnableDefaultSonetaPackageReferences>
</PropertyGroup>

<!-- Następnie można dodać tylko wymagane paczki ręcznie: -->
<ItemGroup>
  <PackageReference Include="Soneta.Products.Modules" Version="$(SonetaPackageVersion)"
                    IncludeAssets="compile;buildTransitive" />
</ItemGroup>
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.