Visual Studio Code Does Not Load Characters in OS X

Question

I am trying to configure web api using ASP.NET Core in OS X. I have set up my environment correctly (I think) and I can create and run my application using dotnet build from the terminal and I can start debugging from Visual Studio code with breakpoints working as expected. My problem is that I get an error when trying to query the Sqlite database using the EF core. The EF core is not very important here, because when I debug and try to figure out what the error is, I don't get the stack trace. When I go to fault-tolerant code, the debug console prints:

 Exception thrown: 'System.InvalidOperationException' in Microsoft.EntityFrameworkCore.dll Loaded '/usr/local/share/dotnet/shared/Microsoft.NETCore.App/1.0.0/System.Diagnostics.StackTrace.dll'. Cannot find or open the symbol file. Loaded '/usr/local/share/dotnet/shared/Microsoft.NETCore.App/1.0.0/System.Reflection.Metadata.dll'. Cannot find or open the symbol file. Loaded '/usr/local/share/dotnet/shared/Microsoft.NETCore.App/1.0.0/System.IO.MemoryMappedFiles.dll'. Cannot find or open the symbol file. Loaded '/usr/local/share/dotnet/shared/Microsoft.NETCore.App/1.0.0/System.IO.UnmanagedMemoryStream.dll'. Cannot find or open the symbol file. 

Many of these Cannot find or open the symbol file. also printed at startup. I checked that the files are in the specified location and that there should not be a problem with access to read (starting with the code using sudo code . And even running sudo chmod 777 * in the corresponding folder).

So, any ideas why the characters are not loading?

Answer 1

Include the same issues as VS code on a Windows 10 virtual machine.

I found a solution to add the "debugType": "portable" parameter to the "debugType": "portable" section of my project.json file.

My looks like this:

 "buildOptions": { "emitEntryPoint": true, "preserveCompilationContext": true, "debugType": "portable" } 

Debugging in VS code is not so bad.

Answer 2

I think you confused what VSCode says it cannot load. He does not say that he cannot load the DLL. Symbol files have the extension .PDB. To debug the error generated by the DLL, the debugger needs an appropriate symbol file, so changing the permissions on the DLL will not result in an error if the PDB file is missing.

I just started using VSCode on Mac and from what I see, you are not getting PDB files if you install the dotnet kernel using Homebrew (this is what they recommend) and I see similar messages when the debugger starts. This does not stop me from debugging my own code, because there is a PDB file generated from my DLL. This will only cause a problem if you need to debug something different than inside the subnet kernel itself.