# Flags to pass to `makeWrapper`. This is done to avoid double wrapping.
,makeWrapperArgs?[]
# Flags to pass to `dotnet restore`.
,dotnetRestoreFlags?[]
# Flags to pass to `dotnet build`.
,dotnetBuildFlags?[]
# Flags to pass to `dotnet test`, if running tests is enabled.
,dotnetTestFlags?[]
# Flags to pass to `dotnet install`.
,dotnetInstallFlags?[]
# Flags to pass to `dotnet pack`.
,dotnetPackFlags?[]
# Flags to pass to dotnet in all phases.
,dotnetFlags?[]
# The path to publish the project to. When unset, the directory "$out/lib/$pname" is used.
,installPath?null
# The binaries that should get installed to `$out/bin`, relative to `$installPath/`. These get wrapped accordingly.
# Unfortunately, dotnet has no method for doing this automatically.
# If unset, all executables in the projects root will get installed. This may cause bloat!
,executables?null
# Packs a project as a `nupkg`, and installs it to `$out/share`. If set to `true`, the derivation can be used as a dependency for another dotnet project by adding it to `projectReferences`.
,packNupkg?false
# The packages project file, which contains instructions on how to compile it. This can be an array of multiple project files as well.
,projectFile?null
# The NuGet dependency file. This locks all NuGet dependency versions, as otherwise they cannot be deterministically fetched.
# This can be generated by running the `passthru.fetch-deps` script.
,nugetDeps?null
# A list of derivations containing nupkg packages for local project references.
# Referenced derivations can be built with `buildDotnetModule` with `packNupkg=true` flag.
# Since we are sharing them as nugets they must be added to csproj/fsproj files as `PackageReference` as well.
# For example, your project has a local dependency:
# Libraries that need to be available at runtime should be passed through this.
# These get wrapped into `LD_LIBRARY_PATH`.
,runtimeDeps?[]
# The dotnet runtime ID. If null, fetch-deps will gather dependencies for all
# platforms in meta.platforms which are supported by the sdk.
,runtimeId?null
# Tests to disable. This gets passed to `dotnet test --filter "FullyQualifiedName!={}"`, to ensure compatibility with all frameworks.
# See https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-test#filter-option-details for more details.
,disabledTests?[]
# The project file to run unit tests against. This is usually referenced in the regular project file, but sometimes it needs to be manually set.
# It gets restored and build, but not installed. You may need to regenerate your nuget lockfile after setting this.
,testProjectFile?""
# The type of build to perform. This is passed to `dotnet` with the `--configuration` flag. Possible values are `Release`, `Debug`, etc.
,buildType?"Release"
# If set to true, builds the application as a self-contained - removing the runtime dependency on dotnet
,selfContainedBuild?false
# Whether to use an alternative wrapper, that executes the application DLL using the dotnet runtime from the user environment. `dotnet-runtime` is provided as a default in case no .NET is installed
# This is useful for .NET tools and applications that may need to run under different .NET runtimes
,useDotnetFromEnv?false
# Whether to explicitly enable UseAppHost when building. This is redundant if useDotnetFromEnv is enabledz
,useAppHost?true
# The dotnet SDK to use.
,dotnet-sdk?dotnetCorePackages.sdk_6_0
# The dotnet runtime to use.
,dotnet-runtime?dotnetCorePackages.runtime_6_0
# The dotnet SDK to run tests against. This can differentiate from the SDK compiled against.