Mac OS: Unhandled Exception: System.TypeInitializationException

[onecentlin]

I installed .NET Core 1.0 official installer released yesterday using this pkg (https://go.microsoft.com/fwlink/?LinkID=809124).
dotnet-dev-osx-x64.1.0.0-preview2-003121.pkg

Version: 1.0.0-preview2-003121

[svick]

According to https://github.com/dotnet/cli/issues/1161, this happens when you don't have openssl installed. Did you follow the guide, especially the "Install pre-requisites" step?

[onecentlin]

Yes, I did have openssl installed.

It was working in 1.0.0.preview1-002702.

[~] $ openssl version
OpenSSL 0.9.8zh 14 Jan 2016

[~] $ which openssl
/usr/bin/openssl

[gguimaraesbr]

+1

[bartonjs]

@onecentlin @gguimaraesbr assuming you used Homebrew to install OpenSSL, it seems like you have only run one of the two commands.

If you run brew link --force openssl that should fix your problem.

The preview1 build could accidentally function without the link step, but we changed the library linking method for RTM (which is in the preview2 build of the sdk tools) to support loading copies from the current directory, which brought back the requirement of having symlinked the library into a system path.

The openssl tool version after that step should be 1.0.2(and a letter); 0.9.8 is not supported.

[onecentlin]

@bartonjs Thank you. This works!!
I did link openssl before while developing with RC2.

After executing the command, now it works perfectly.

$ brew link --force openssl
Linking /usr/local/Cellar/openssl/1.0.2h_1... 1601 symlinks created

[ascarter]

@onecentlin can you run which openssl? I followed the instructions for brew link but it still is using 0.9.8 (system openssl) for me. Curious to see what path yours has since it works.

[onecentlin]

@ascarter This is my openssl version and path.

$ openssl version
OpenSSL 1.0.2h  3 May 2016

$ which openssl
/usr/local/bin/openssl

[bartonjs]

@ascarter It's possible to have the /usr/bin/openssl version as a higher precedent in your path. The important part is whether libcrypto.1.0.0.dylib is on the library loader path. If you use Homebrew and brew link, then it'll be in /usr/local/lib/. $HOME/lib/ and /usr/lib/ are also acceptable locations (by default), (https://developer.apple.com/library/mac/documentation/DeveloperTools/Conceptual/DynamicLibraries/100-Articles/DynamicLibraryUsageGuidelines.html#//apple_ref/doc/uid/TP40001928-SW21 for more information)

[mikeho]

Is there a particular reason why brew's version of OpenSSL is recommended (or required)?

I am using MacPorts for all of my package management, and I can confirm that I am using the latest version of OpenSSL:

$ which openssl
/opt/local/bin/openssl
$ openssl version
OpenSSL 1.0.2h  3 May 2016

The opt-releated paths are set up correctly in my PATH settings and show up first (which is the default approach for MacPorts).

Yet I'm getting the same error that others are reporting:
Unhandled Exception: System.TypeInitializationException: The type initializer for 'Crypto' threw an exception. ---> System.TypeInitializationException: The type initializer for 'CryptoInitializer' threw an exception...

Is the dotnet command line not able to utilize the PATH setting to locate the openssl files to use?

EDIT: I have also symlinked the macports version of libcrypto and libssl into /usr/local/lib, but I'm still getting the same error/issue.

[gguimaraesbr]

Thanks @bartonjs Symlinking the library did the trick.

[bartonjs]

@mikeho $PATH is only for execution, and the openssl utility isn't actually used. What we need is libcrypto.1.0.0.dylib and libssl.1.0.0.dylib; and they need to be in a standard rpath probing location, which is any of $HOME/lib, /usr/local/lib/, /usr/lib/, or the current directory.

Or you can try altering the DYLD_LIBRARY_PATH environment variable to include /opt/local/lib (which is where I assume MacPorts put it); but the Internet seems full of people who complain that DYLD_LIBRARY_PATH overrides aren't as successful as advertised on El Capitan.

Personally, I'd just add symlinks in /usr/local/lib to those two libraries wherever MacPorts put them (unless MacPorts has a command similar to brew link, which puts them in that path for you... then I'd run that).

[ascarter]

@bartonjs Thanks - I think you are exactly right. I install homebrew in /opt/homebrew to keep it isolated and I think that's precisely why I don't see the paths the same. I can make it work out.

[mikeho]

@bartonjs looks like our messages got crossed over the wire.

I actually did go ahead and symlink the macports version of libcrypto.1.0.0.dylib and libssl.1.0.0.dylib into /usr/local/lib, but I'm still getting the same error/issue.

[bartonjs]

@mikeho Intriguing. I don't suppose you can give me a primer on making my machine look like yours? (Like, how to get/use MacPorts, what options you've used (if applicable) and manual symlink commands you've done to try to remediate).