CLR is the .net execution environment where all kind of .net applications are run.For instance, when you write your code with C# or another language from the dot NET stack the compiler compiles and converts it into managed module.
.net - CLR and CLI - What is the difference? - Stack Overflow
I googled CLR and found out what it is from wikipedia, but I wanted to know what a CLR class or more specifically a CLR entity type is (especially in ASP.NET).
However the CLR design mandates that the JIT happens before the relevant code executes, JVMs in contrast would be free to interpret the code for a while while a separate thread creates a machine code representation. The 'normal' CLR uses a pre-JIT stub approach where by methods are JIT compiled only as they are used.
CLR with C# 3.0 is a good book however eventually it isn't a IL book so it doesn't explain everything about IL. EDIT: I've found the specs and they tell these: Thanks to @usr. nop (for debugging - no operation) newobj - create a new object stloc.0 - pop value from stack to local variable ldloc.0 ? - load local variable onto the stack
.net - How to Learn IL on the CLR - Stack Overflow
When building or running tests in any C# projects from a PowerShell command line (dotnet build or dotnet test) I get a "Fatal error. Internal CLR error" ...
In the case if tSQLt, it uses CLR objects to provide unit testing functionality that cannot be accomplished with the T-SQL language. Enabling CLR does add to the surface area so it should only be enabled when you need it.