Problem running dotnet run command

[jgp023]

Problem encountered on https://dotnet.microsoft.com/learn/dotnet/hello-world-tutorial/run
Operating System: macos

Provide details about the problem you are experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

hello world does not populate in the terminal. the error message says
Unhandled exception. System.IO.FileNotFoundException: Could not load file or assembly '/Users/jordan_g.o.a.t./myApp/bin/Debug/netcoreapp3.1/myApp.dll'. The system cannot find the file specified.

File name: '/Users/jordan_g.o.a.t./myApp/bin/Debug/netcoreapp3.1/myApp.dll'

[scalablecory]

@jeffschwMSFT what would cause this?

[jeffschwMSFT]

@lpereira did we investigate paths that have '.'s at the end? What was the outcome?

[lpereira]

We did; the issue is that Windows ignores the . in a path name if it precedes a /, so the function to convert a Unix path name to a Windows pathname will strip it. I decided not to fix this in order to keep it compatible with Windows; however, I remember @mateoatr looking at this right after he joined the team and sending a PR to not strip that dot on Unix. I think that PR has been merged.

Maybe it should also be backported to the next 3.1 release?

[mateoatr]

This is the PR for reference.

[carlossanlop]

The fix for this issue has been merged. @mateoatr, in which version should we expect the fix to be available?

[mateoatr]

This should've been working since 3.1.1, however I just ran into the same problem. I'll take a look at it.

[carlossanlop]

@mateoatr did you get a chance to take a look?

[mateoatr]

@mateoatr did you get a chance to take a look?

The aforementioned PR was merged for .NET 5 - not .NET Core 3.1 (my bad); so this is currently working. If necessary I can backport the PR to 3.1.

[mairaw]

The tutorials on the dotnet.microsoft.com won't be upgraded until we reach .NET 6, since we'll keep using the LTS version.
Is that a common issue?

[mateoatr]

I don't know how common it is, I'd guess not too common. And, realistically, it only affects Unix, since ending a directory name with a period violates Windows' naming conventions.