Question 1

How to reference a NuGet package in Nake?

Accepted Answer

Use the #r "nuget: PackageName" syntax in your script, similar to dotnet-script. For example, #r "nuget: Newtonsoft.Json" pulls in JSON.NET without separate config files. This leverages dotnet-script's dependency resolution system.

Question 2

Nake vs Cake: which is better for .NET builds?

Accepted Answer

Nake uses plain C# code as its DSL, offering more flexibility and modern features, while Cake has a custom DSL with a larger ecosystem. Choose Nake if you prefer writing build logic in standard C#; opt for Cake if you need extensive community plugins and templates.

Question 3

How do I run multiple tasks in one go with Nake?

Accepted Answer

Separate tasks with semicolons in the command line, like Nake build ; test. In PowerShell, escape the semicolon with a backtick. This allows chaining executions within a single session, as shown in the command line reference.

Question 4

Can Nake scripts be made executable on Unix-like systems?

Accepted Answer

Yes, use the polyglot shebang from the README: add #!/usr/bin/env bash and the provided code, then run chmod +x on the file. This makes scripts directly runnable, supporting cross-platform automation.

Question 5

How does Nake handle environment variables dynamically?

Accepted Answer

It supports inline access with $var$ syntax, which evaluates at compile-time or runtime based on scope. For example, var key = "$APIKEY$" retrieves the value when invoked, while constants inlined at compile-time.

Question 6

Is Nake good for large teams with complex build pipelines?

Accepted Answer

It can be, due to its code-driven flexibility, but it lacks built-in governance features like audit trails or integrations with CI/CD platforms. Teams might need to supplement it with other tools for enterprise-scale workflows.

Nake

What is Nake?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions