The answer is yes, but the solution is a little tricky. The System.Reflection.Emit namespace defines types that allows assemblies to be generated dynamically. They also allow the generated assemblies to be defined incrementally. In other words it is possible to add types to the dynamic assembly, execute the generated code, and then latter add more … Read more
Surprisingly, it depends. If you do this in a method: void Foo() { String one = “1”; String two = “2”; String result = one + two + “34”; Console.Out.WriteLine(result); } then the compiler seems to emit the code using String.Concat as @Joachim answered (+1 to him btw). If you define them as constants, e.g.: … Read more
This isn’t well documented in any place I know of, I can only point you to a relevant MSDN article. Yes, your assumption is correct, the loader in Windows XP and up has awareness of managed executables. It automatically loads the .NET loader shim (c:\windows\system32\mscoree.dll), the relevant entrypoint is _CorValidateImage(). The Remarks section in the … Read more
This answer is not talking about C#, but it helped me understand the issues better and maybe it will help others: Why is there no parameter contra-variance for overriding?
Note: this answer is on a “per-run” context. The code is normally JITted each time you run the program. Using ngen or .NET Native changes that story, too… Unlike HotSpot, the CLR JIT always compiles exactly once per run. It never interprets, and it never recompiles with heavier optimisation than before based on actual usage. … Read more
The short answer: interning literal strings is cheap at runtime and saves memory. Interning non-literal strings is expensive at runtime and therefore saves a tiny amount of memory in exchange for making the common cases much slower. The cost of the interning-strings-at-runtime “optimization” does not pay for the benefit, and is therefore not actually an … Read more
There are a lot of misconceptions here. I suppose you could think of .Net as a virtual machine if you really wanted, but let’s look at how the .Net Framework really handles your code. The typical scenario looks like this You write a .Net program in C#, VB.Net, F#, or some other compatible language. That … Read more
You can use _com_error: _com_error err(hr); LPCTSTR errMsg = err.ErrorMessage(); If you don’t want to use _com_error for whatever reason, you can still take a look at its source, and see how it’s done. Don’t forget to include the header comdef.h
The following copied from Don Box’s excellent Essential .Net. (available here) (and, imho, a must have for any professional .Net developer) The CLR Loader The CLR Loader is responsible for loading and initializing assemblies, modules, resources, and types. The CLR loader loads and initializes as little as it can get away with. Unlike the Win32 … Read more
According to Reflector: public override int GetHashCode() { return this; } Makes sense, does it?