OSX 10.13 DOTNET RUN System.ComponentModel.Win32Exception (0x80004005): No such file or directory

[fbarletta]

When executing dotnet run -c release in my terminal on OSX 10.13, I get the following error:

../../Properties/launchSettings.json... System.ComponentModel.Win32Exception (0x80004005): No such file or directory at Interop.Sys.ForkAndExecProcess(String filename, String[] argv, String[] envp, String cwd, Boolean redirectStdin, Boolean redirectStdout, Boolean redirectStderr, Int32& lpChildPid, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean shouldThrow) at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo) at System.Diagnostics.Process.Start() at Microsoft.DotNet.Cli.Utils.Command.Execute() at Microsoft.DotNet.Tools.Run.RunCommand.Start() at Microsoft.DotNet.Tools.Run.RunCommand.Run(String[] args) at Microsoft.DotNet.Cli.Program.ProcessArgs(String[] args, ITelemetry telemetryClient) at Microsoft.DotNet.Cli.Program.Main(String[] args)

.NET Command Line Tools (2.2.0-preview1-007582)

Product Information:
Version: 2.2.0-preview1-007582
Commit SHA-1 hash: 4845efe2ea

Runtime Environment:
OS Name: Mac OS X
OS Version: 10.13
OS Platform: Darwin
RID: osx.10.12-x64
Base Path: /usr/local/share/dotnet/sdk/2.2.0-preview1-007582/

Microsoft .NET Core Shared Framework Host

Version : 2.1.0-preview1-25919-02
Build : 96a1025de48784825ac61e45ece24a4343e0bf01

The runtime identifier is set for <RuntimeIdentifier>osx.10.12-x64</RuntimeIdentifier> or osx-x64 as directed on the Microsoft documents.
The project works on Windows 10, just not on any OSX device.
The launchSettings.json file does exist. If I copy and nano the file, it will edit the file. I'm out of ideas right now.

[richlander]

Do you have a minimal repro you can share?

[fbarletta]

I don’t It’s a very complex app and striping it down would be impossible at this point. On November 29, 2017 at 2:06 AM, Rich Lander <notifications@github.com> wrote: Do you have a minimal repro you can share? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1119 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEHAc0jGGZ6M5XXTyCLAG78ESwFove64ks5s7QJ3gaJpZM4QuKAn> .

[fbarletta]

I will mention that it works perfectly on Windows 10. It's multiple apps we've created and we used to be able to run on dotnetcore 1.0 on osx 10.12 but we've since iterated the products and haven't used os x until now. It's a stopper for us so any help is appreciated.

Is there no compatibilty with os High Sierra?

[Petermarcu]

Are you able to dotnet publish -r osx.10.12-x64 and then run the resulting output in the publish folder?

[fbarletta]

When I run the command `dotnet publish -r osx.10.12-x64` it creates the folder properly. Then, I enter the folder and `dotnet run` and I get an error `Couldn't find a project to run. etc`

…

On Wed, Nov 29, 2017 at 12:45 PM, Peter Marcu ***@***.***> wrote: Are you able to dotnet publish -r osx.10.12-x64 and then run the resulting output in the publish folder? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1119 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEHAc8tB0e7Ag__q9WD4TPJARdo7AOWZks5s7ZhHgaJpZM4QuKAn> .

-- Francis Barletta CEO UPTOP www.liveuptop.com

[Petermarcu]

yeah, don't dotnet run in that folder just run your app. If your app is called foo just run foo.

[Petermarcu]

Note that dotnet run is really just for development. We should figure out how to make it work but once you have an app you want to run in production, you should always publish it and not use dotnet run.

[fbarletta]

run <appname> does not work. I'm using Terminal on OSX.

Yes, dotnet run is for dev and this is dev at the moment. When we push to production, we publish.

The problem is, we cannot get the dev environment to run on OSX.

[fbarletta]

I just ran some tests and found out that project creates projectname.projectname I've read this is an issue on osx high sierra

…

On Wed, Nov 29, 2017 at 2:23 PM, Peter Marcu ***@***.***> wrote: Note that dotnet run is really just for development. We should figure out how to make it work but once you have an app you want to run in production, you should always publish it and not use dotnet run. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1119 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEHAcwlniHEdEfIXgqwGb0RlwgPleKThks5s7a9CgaJpZM4QuKAn> .

-- Francis Barletta CEO UPTOP www.liveuptop.com

[Petermarcu]

What if you leave off the run and do .\appname?

[dasMulli]

This is https://github.com/dotnet/cli/issues/6397 again

I've been chatting on slack with @fbarletta and it turns out that the executable is published under a wrong name

[dasMulli]

I can reproduce this on the 2.2.0-preview1-007582 CLI like this:

• dotnet new console -o testcons
• cd testcons
• mv testcons.csproj test.cons.csproj
• change project content to

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>netcoreapp2.0</TargetFramework>
    <RuntimeIdentifier>osx-x64</RuntimeIdentifier>
  </PropertyGroup>

</Project>

• dotnet build

=>

Martins-MacBook-Pro:testcons martin$ ls -l bin/Debug/netcoreapp2.0/osx-x64/
total 3552
-rwxrw-rw-  1 martin  staff  768928 20 Jul 16:11 libhostfxr.dylib
-rwxrw-rw-  1 martin  staff  880968 20 Jul 16:11 libhostpolicy.dylib
-rwxrw-rw-  1 martin  staff  123596 29 Nov 20:38 test.cons.cons
-rw-r--r--  1 martin  staff   19620 29 Nov 20:38 test.cons.deps.json
-rw-r--r--  1 martin  staff    3584 29 Nov 20:38 test.cons.dll
-rw-r--r--  1 martin  staff     416 29 Nov 20:38 test.cons.pdb
-rw-r--r--  1 martin  staff     212 29 Nov 20:38 test.cons.runtimeconfig.dev.json
-rw-r--r--  1 martin  staff      26 29 Nov 20:38 test.cons.runtimeconfig.json

the executable is named test.cons.cons => breaks dotnet run and needs to be renamed in order to run correctly

[dasMulli]

msbuild.binlog.zip

[Petermarcu]

Im on Windows and publishing a 2.0 app for osx-x64 and the app name isn't mangled. @livarcocc I assume you want this conversation to continue on https://github.com/dotnet/cli/issues/6397 and close this one here?

[Petermarcu]

I'm going to close this issue here and reopened the one on the CLI where the discussion can continue. Thanks!