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.
btw, all the time when I am reading api reference I wonder if the documentation could be improved in one area, that is all this cross platform stuff. there are tons of seemingly windows specific apis that do work on unix, even sometimes without too much emulation, and they are not even documented as working on unix. or another way around, things not declared not to work on unix, while they possibly could. My fawourite is GetLastWin32Error that probably works on unix.
@webczat welp, https://github.com/dotnet/dotnet-api-docs/blob/master/xml/System.Runtime.InteropServices/Marshal.xml PR's are welcome =D
Would it be possible to obsolete GetLastWin32Error and make a GetLastError instead? just curious if it makes sense to report such things. still this method is confusing, especially when you realize it works on non win32...
but it would probably break compat...
(because WarningAsErrors)
(the roslyn team hasn't added new warnings to existing language features for this exact reason)
new warnings to existing language features? what do you mean?
the compat bar for the C# compiler is ridiculously high
but it looks like warning waves are comming soon which would mean you can opt into new warnings
they're also working on a new system to improve API deprecation: https://github.com/dotnet/designs/pull/62/files
so while they types are still there the runtime behaviour is probably simpler and close to "normal"
anybody have recommendation to find Types at startup time in an app
it seems that if i create 1 classlib and 1 console app referencing the classlib "discovery" (using AssemblyLoadContext) wont find the libs types
once i interact with a type from the classlib like var foo = new TypeFromLib it does find it
i guess there it's kinda logic not to load stuff (lazy loading like)
we are trying to find "all"
protobuf generated types in order to register them (we wrote a Signalr IHubProtocol) but we do need to have the list of known message that we will need to deserialize
any recommandation ?
well simple...eyes :sweat_smile:
I have a feeling it may not be universally understood
No idea if it's closer to 80% or 8% :P
(and it is one of the few emoticons supported as GitHub reactions)
for another example of a very broadly-defined emoji: https://blog.emojipedia.org/emojiology-upside-down-face/
I may or may not be distantly related to some of these people
Hi all, apologies, anyone familiar with using .NET c# to manipulate VISIO files without calling the VISIO application. There is a tutorial on manipulating the VISIO file as an XML, https://docs.microsoft.com/en-us/office/client-developer/visio/how-to-manipulate-the-visio-file-format-programmatically but it doesn't cover insertion. Use case is a batch process in a server that will add a watermark/classification image to the files eg, "DRAFT" , "SAMPLE" , "APPROVED". Thank you.
