Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Following "Getting started in seconds" gives: Namespace "FileSystemTasks" does not exist error #1512

Closed
normalvector opened this issue Feb 5, 2025 · 0 comments
Labels
Milestone

Comments

@normalvector
Copy link

Usage Information

Nuke 9.0.4, .NET SDK 9.0.101, Windows 11

Description

While following the "Getting Started in Seconds" on the website Nuke installs and the :setup runs, but then running any Nuke command gives "error CS0234: The type or namespace name 'FileSystemTasks' does not exist in the namespace 'Nuke.Common.IO' (are you missing an assembly reference?)"

This happened even in an empty directory with Nuke being reinstalled fresh, as shown in the reproduction steps below.

Reproduction Steps

Here's a lot of me running the "Getting started in seconds" commands in an empty directory to show the error in a Windows console, and accepting defaults for the setup:

C:\nuke_test>dir
Volume in drive C is Main SSD
Volume Serial Number is 40AE-A58D

Directory of C:\nuke_test

05/02/2025 18:58

.
0 File(s) 0 bytes
1 Dir(s) 1,833,250,914,304 bytes free

C:\nuke_test>dotnet tool uninstall Nuke.GlobalTool --global
Tool 'nuke.globaltool' (version '9.0.4') was successfully uninstalled.

C:\nuke_test>dotnet tool install Nuke.GlobalTool --global
You can invoke the tool using the following command: nuke
Tool 'nuke.globaltool' (version '9.0.4') was successfully installed.

C:\nuke_test>nuke :setup
NUKE Global Tool 🌐 version 9.0.4 (Windows,.NETCoreApp,Version=v8.0)

Let's setup a new build!

Could not find root directory. Falling back to working directory ...
🌳 Root directory: C:\nuke_test
🔖 Build project name: _build
📍 Build project location: ./build
💎 Nuke.Common version: 9.0.4
🧰 Default solution:

Setup completed! 🎉

C:\nuke_test>nuke
PowerShell Desktop version 5.1.22621.4391
Microsoft (R) .NET SDK version 9.0.101
C:\nuke_test\build\Build.cs(11,29): error CS0234: The type or namespace name 'FileSystemTasks' does not exist in the namespace 'Nuke.Common.IO' (are you missing an assembly reference?)

C:\nuke_test>nuke clean
PowerShell Desktop version 5.1.22621.4391
Microsoft (R) .NET SDK version 9.0.101
C:\nuke_test\build\Build.cs(11,29): error CS0234: The type or namespace name 'FileSystemTasks' does not exist in the namespace 'Nuke.Common.IO' (are you missing an assembly reference?)

C:\nuke_test>nuke --help
PowerShell Desktop version 5.1.22621.4391
Microsoft (R) .NET SDK version 9.0.101
C:\nuke_test\build\Build.cs(11,29): error CS0234: The type or namespace name 'FileSystemTasks' does not exist in the namespace 'Nuke.Common.IO' (are you missing an assembly reference?)

Expected Behavior

The Nuke commands should run without errors

Actual Behavior

C:\nuke_test>nuke
PowerShell Desktop version 5.1.22621.4391
Microsoft (R) .NET SDK version 9.0.101
C:\nuke_test\build\Build.cs(11,29): error CS0234: The type or namespace name 'FileSystemTasks' does not exist in the namespace 'Nuke.Common.IO' (are you missing an assembly reference?)

Regression?

Don't know, only trying out Nuke for the first time and not confident I can get this investigated quickly.

Known Workarounds

The 'using' line can be commented out to fix it but this is happening in the basic introduction

Could you help with a pull-request?

No

@matkoch matkoch added this to the v9.0.5 milestone Feb 5, 2025
@matkoch matkoch pinned this issue Feb 5, 2025
@matkoch matkoch closed this as completed Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants