Script compilation not working on MacOS

[broberson]

Describe the bug
Fails to compile files in the Scripts directory on MacOS. Full error is:

02/14/2024 11:30:53 | Error | System.TypeInitializationException: The type initializer for 'Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CompilationUtil' threw an exception. ---> S
ystem.EntryPointNotFoundException: IsDebuggerPresent assembly: type: member:(null)
at (wrapper managed-to-native) Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CompilationUtil.IsDebuggerPresent()
at Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CompilationUtil.get_IsDebuggerAttached () [0x00000] in <4d7629dbeba24b9aa3bac2e83ed1f745>:0
at Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CompilationUtil.GetProviderOptionsFor (System.String fileExt) [0x000ee] in <4d7629dbeba24b9aa3bac2e83ed1f745>:0
at Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CompilationUtil..cctor () [0x00000] in <4d7629dbeba24b9aa3bac2e83ed1f745>:0
--- End of inner exception stack trace ---
at Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider..ctor (Microsoft.CodeDom.Providers.DotNetCompilerPlatform.IProviderOptions providerOptions) [0x00006] in <4d7629dbeba24b9aa3bac2e83ed1f745>:0
at Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider..ctor () [0x00000] in <4d7629dbeba24b9aa3bac2e83ed1f745>:0
at (wrapper remoting-invoke-with-check) Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider..ctor()
at ClassicUO.ScriptCompiler.CompileCSScripts (System.Boolean debug, System.Boolean cache, System.Reflection.Assembly& assembly) [0x00121] in <04f23b2052a348fc85eb1a9d16fc0176>:0
at ClassicUO.ScriptCompiler+<>c__DisplayClass28_0.b__0 () [0x00031] in <04f23b2052a348fc85eb1a9d16fc0176>:0

This system has the dotnet SDKs installed from Microsoft, as well as mono from homebrew. ServUO (pub57) is currently running on this system as well, and it compiles its scripts successfully in this environment.

To Reproduce
Steps to reproduce the behavior:

• Downloaded and extracted the latest bleeding edge build for MacOS from here: https://github.com/bittiez/TazUO/releases
• Added ItemSearch.cs to the TazUO/Scripts directory from here: https://github.com/bittiez/TazUO-Scripts/blob/main/ItemSearch.cs
• Ran TazUO from a terminal with ./ClassicUO to see the console output. The above compilation error shows up in the runtime output, no Scripts.CS.dll file is created, and once the login window loads and I log into a shard, the command defined in the script is not recognized by the client.

Expected behavior
I'd expect the scripts directory to be compiled.

Shard

• Name of the shard: none, a local ServUO instance was used for testing. The problem occurs before the user interface even loads, and no connection needs to be made to a shard to see the problem.

Information (please complete the following information):

• OS: MacOS Sonoma 14.2.1 on a 2019 Intel-based Macbook Pro
• ClassicUO Version: v3.20.0 v3.20.0 #212
• Using DEV Version?
• Launcher: Command Line (same results with ClassicUO Launcher, but the console output isn't visible)

Additional context

• How many clients do you run in parallel: just one client at the moment.
• Screen Resolution: 1920x1080

[bittiez]

Hmm, do you have debugging enabled via args when running TUO?

[broberson]

No, I don't

[bittiez]

Okay, confirmed the issue is also on Linux, I will have to see what I can figure out