Error resolving OmniSharp runtime dependencies in MacOS bundles

[derek-knox]

Problem

We are developing a cross-platform app (Windows & MacOS) that bundles OmniSharp v1.39.13 and runs it in a subprocess.

• Windows (works as expected)
• MacOS (fails due to OmniSharp stderr: The application to execute does not exist: '.../SomeApp.app/Contents/MacOS/OmniSharp.dll')

The core issue is that the OmniSharp binary is placed in one dir (Contents/MacOS) but its runtime dependencies in another (Contents/Resources). This is a constraint of MacOS app guidelines (as I understand it).

On Windows all these files are collocated in the root of the app so the adjacent runtime dependencies resolve successfully. On MacOS, they are not collocated.

  SomeApp.app/Contents/
  ├── MacOS/
  │   └── SomeApp          
  │   └── OmniSharp          # ✅ Executable binary (correct location)
  └── Resources/
      ├── OmniSharp.dll      # ✅ .NET assembly (correct location per Apple)
      └── other-deps...      # ✅ Other dependencies (correct location per Apple)

Questions

1. Is there a setting, configuration, CLI flag, or similar so that we can tell OmniSharp to resolve to a relative path?
2. Any general thoughts or tips come to mind regarding our scenario?

[JoeRobich]

Can the executable in the MacOS folder be a shell script which invokes OmniSharp from the Resources folder?

[derek-knox]

Can the executable in the MacOS folder be a shell script which invokes OmniSharp from the Resources folder?

@JoeRobich This is something that crossed our mind initially, but as we understand it all binaries must be signed and placed in MacOS dir. Something we can still explore, so thanks for the feedback.

Just to confirm, there is no missing setting/flag/config we should be using to make OmniSharp resolve dependencies in a relative dir. Is that correct?

[JoeRobich]

@derek-knox The OmniSharp executable from the .NET builds is the default .NET apphost. It seems like your request is related to dotnet/sdk#10366

As an alternative to using this prebuilt apphost, you can use dotnet CLI as your apphost by invoking dotnet .../Resources/OmniSharp.dll -- ...