Skip to content
Discussion options

You must be logged in to vote

We consider the coreclr.dll to be an internal implementation detail. We do know that it's used by some hosts, but we actively discourage people from doing that. And we may decide to break it in the future - for example #52688 could break your host (depends on how you're using coreclr) if we decide to do it.

There are also functional reasons for this - for example AssemblyDependencyResolver will not work if the runtime is hosted without hostfxr/hostpolicy.

So in short I would suggest you strongly consider moving your code to the hostfxr APIs. It should also simplify your code as hosting the runtime directly usually needs more setup code.

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@MAAC-2018
Comment options

Answer selected by teo-tsirpanis
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants