This repo contains the .NET Core runtime, called CoreCLR. It is an execution engine for .NET apps, performing functions such as IL byte code loading, compilation to machine code and garbage collection. The repo contains the complete up-to-date CoreCLR codebase.
Perhaps
5.0.100-rc.2.20479.15 ("full version" from https://dotnet.microsoft.com/download/dotnet/5.0)?
@john-cullen I learned originally from Jeffrey Richter when he was writing back in the .Net 3.5 days-ish. For .net core the fusion log viewer I don't think works...but I know there is an environment variable you can set that will cause .net core to start spewing out TONS of log info to console-out that tells you in nauseating detail what assemblies it is loading and where it is searching for them.
Just want to thank anyone who worked on .NET 5 - the perf. boost I see so far is beyond any expectations: https://twitter.com/alexyakunin/status/1326438626901729280
What is the idiomatic way to log by application feature? Using Microsoft.Extensions.Logging but in a very custom server setup. So we have an AppLogger class with static methods that proxy to the system wide logger. We have no good reason for separate logger instances. So I threw together a LogScoped method that takes an AppLogScope enum. That grabs a LogLevel constant defined for the scope.
DI would be nice but it's not so simple, multiple context's we would have to create injectors for. So atm DI for logging just not a good bang for buck
If I have a .NET Core exe referencing a .NET Framework Dependency, and that .NET framework dependency has another .NET framework dependency, is it possible to redirect that 3rd dependency. We can't use GAC/policy files, but is there some kind of file I can use to do a .NET Framework assembly binding redirect even if I am running in .NET Core 3.1?
if so, then yes it'll be blocked, because there is no way to actually express that in IL today
the runtime team has been wanting to introduce something in that space for some time now, and the lang team has just put the corresponding feature in the 10.0 Working Set (which isn't a guarantee of anything, but it does mean they're going to look into it)
Span uses an internal type for a hack workaround, but the runtime team wants to remove that implementation detail
And of course ByREference<T> is hidden so I can't reuse it.
I'm trying to model rust's "ref" semantics on the clr
I don't care much if it's safe or not
But they would require pinning.
But it would become a c++ level language pretty quickly.
It's getting a bit off topic
thanks for the help
I want to see if it's possible to map rust now
