Fallout.Migrate.Analyzers
10.4.0
Prefix Reserved
dotnet add package Fallout.Migrate.Analyzers --version 10.4.0
NuGet\Install-Package Fallout.Migrate.Analyzers -Version 10.4.0
<PackageReference Include="Fallout.Migrate.Analyzers" Version="10.4.0"> <PrivateAssets>all</PrivateAssets> <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets> </PackageReference>
<PackageVersion Include="Fallout.Migrate.Analyzers" Version="10.4.0" />
<PackageReference Include="Fallout.Migrate.Analyzers"> <PrivateAssets>all</PrivateAssets> <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets> </PackageReference>
paket add Fallout.Migrate.Analyzers --version 10.4.0
#r "nuget: Fallout.Migrate.Analyzers, 10.4.0"
#:package Fallout.Migrate.Analyzers@10.4.0
#addin nuget:?package=Fallout.Migrate.Analyzers&version=10.4.0
#tool nuget:?package=Fallout.Migrate.Analyzers&version=10.4.0
Fallout.Migrate.Analyzers
Roslyn analyzer + codefix that rewrites legacy Nuke.* references to Fallout.* in C# source. Install it temporarily while migrating; uninstall once you're done.
What it does
Emits a single diagnostic, FALLOUT004 (severity: Warning), at each of:
using Nuke.<X>;directivesusing static Nuke.<X>.<Y>.<Type>;directives- Fully-qualified type references like
Nuke.Common.AbsolutePath - Bare type names
NukeBuildandINukeBuild
The codefix rewrites all of those to their Fallout.* equivalents in a single edit (Migrate to Fallout.*), including the type renames (NukeBuild → FalloutBuild, INukeBuild → IFalloutBuild). Fix all in Document / Project / Solution is supported.
How to use
dotnet add build/_build.csproj package Fallout.Migrate.Analyzers
Open your build project in an IDE that supports Roslyn analyzers (Visual Studio, Rider, VS Code with C# Dev Kit). Each FALLOUT004 site becomes a lightbulb / quick-fix; apply individually or Fix all in Solution.
When the diagnostic count drops to zero:
dotnet remove build/_build.csproj package Fallout.Migrate.Analyzers
What it does not do
- It does not update
PackageReferenceitems in your_build.csproj— that's outside Roslyn's domain. Once the source is migrated, swapNuke.CommonforFallout.Common(and friends) in your project file by hand. - It does not touch bootstrap scripts (
build.ps1,build.sh,build.cmd). Those keep their names. - It does not fire on pure-NUKE projects (no
Fallout.*reference present). The diagnostic is guarded byCompilation.ReferencedAssemblyNames— you have to be partway into the migration before warnings appear.
Alternative: bulk rewrite via CLI
If you want to migrate an entire repo in one shot from the command line, use the fallout-migrate global tool instead. It does the same rewrites plus updates PackageReferences and bootstrap scripts.
Deprecation
This package will be removed alongside the Nuke.Common transition shim. Track the shim's deprecation timeline in docs/rebrand-plan.md. Plan: ship through the 11.x line, remove in 12.0.
Learn more about Target Frameworks and .NET Standard.
This package has no dependencies.
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 10.4.0 | 132 | 8/7/2026 |
| 10.4.0-rc.5 | 61 | 7/29/2026 |
| 10.4.0-rc.4 | 53 | 7/26/2026 |
| 10.3.49 | 123 | 5/29/2026 |
| 10.3.47 | 115 | 5/27/2026 |
| 10.3.45 | 113 | 5/27/2026 |
| 10.3.44 | 109 | 5/27/2026 |
| 10.3.42 | 127 | 5/27/2026 |