Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Probe for DOTNET_REFERENCE_ASSEMBLIES_PATH on Mono

See original GitHub issue

Right now, to build for net451 on non-Windows, you have to set DOTNET_REFERENCE_ASSEMBLIES_PATH to a folder containing the Mono reference assemblies. We should support scanning a few default locations for this.

/cc @victorhurdugaci @davidfowl

Issue Analytics

State:
Created 8 years ago
Comments:15 (9 by maintainers)

Top GitHub Comments

1reaction

troydaicommented, Mar 11, 2016

Fixed in 429625061dc64bf1b8a53d140486b301612b2727

0reactions

troydaicommented, Mar 11, 2016

Sure: https://github.com/aspnet/KoreBuild/issues/34

Top Results From Across the Web

How the Runtime Locates Assemblies - .NET Framework

Learn how the common language runtime (CLR) locates and binds to the assemblies that make up your application in .NET.

Assemblies and the GAC

The Mono runtime allows you to reference multiple GACs and the Mono gacutil will allow you to create GACs in multiple locations. These...

Injecting a an assembly reference /w Mono Cecil does not ...

Assembly probing works differently on dotnet core. The following sample works as expected once I update the app.deps.json file accordingly.

How to resolve “Could not load file or assembly … or one of its ...

Code base or Probing: First checks in location in <codeBase> element. If not present, then probing is done in Application base considering culture,...

Using the ReferenceAssemblies NuGet package to build . ...

In this post I show how you can build .NET projects that target .NET Framework versions on Linux, without using Mono. By using...