clr

Will .Net 4.0 use a new version of the CLR (v2.1, 3.0) or will it stick with the existing v2.0? Supplementary: Is it possibly going to keep with CLR v2.0 and add DLR v1.0? Update: Whilst this might look like a speculative question which cannot be answered, the VS team appear to be releasing more and more info on VS10 and .Net 4.0 so this may very soon not be the case. (Info available here -> http://msdn.microsoft.com/en-us/vstudio/products/cc948977.aspx ) 4.0 is going to be another side by side release from what I have read. http://blogs.msdn.com/wenlong/archive/2008/09/07/net-4-0-wf-wcf-and

This post says that it is possible to turn off the CLR flag for an individual .cpp file. From the post: You can set /CLR on or off in each .cpp file individually. Turn it on for the whole project,. as you have done, then turn it off for the files containing only native (unmanaged) code. When you have the VC++ procject properties dialog open, you can still click on files/projects in the solution explorer to change the scope that you're working on. Click on the unmanaged .cpp file to set options for just that file. Is this true? I can't figure out how to do it through the property pages for my C

Due to the huge resources behind it, Javascript seems to rapidly becoming the scripting language of choice for applications, particularly those with a web front end. I have an application that requires extensibility both on the front and backend. Javascript, or a thin wrapper like CoffeeScript, seems like an excellent, future-oriented, choice. The problem I'm having with using Javascript as the target is interoperability with existing server side libraries. V8 requires custom C++ code. I'd much prefer to leverage the vast resources of the JDK/.NET class libraries and our code that exposes APIs

Please consider the following code: public async Task<string> GetString() { //Some code here... var data = await A(); //Some more code... return data; } private async Task<string> A() { //Some code here.. var data = await B(); //manipulating data... return data; } private async Task<string> B() { //Some code here.. var data = await C(); //manipulating data... return data; } private async Task<string> C() { //Some code here.. var data = await FetchFromDB(); //manipulating data... return data; } private async Task<string> FetchFromDB() { return await SOME_HTTP_REQUEST; } This code demonstrate a

How are extension methods implemented internally? I mean what happens when the compiler sees a declaration for an extension method and what happens at runtime when there is a call to an extension method. Is reflection involved? Or when you have an extension method is its code injected in the target class type metadata with some additional flags noting that this is an extension method and then the CLR knows how to handle that? So in general, what happens under the hood? As already have said by other colleagues it is just a static method. It is all about the compiler we can say that CLR even

Possible Duplicate: How do foreach loops work in C#? I've been searching the internet and I'm having trouble finding any answers as to what's really going on behind the scenes with the foreach loop in C#. I know this question doesn't really pertain to actually coding but its bothering me. I'm pretty new to OO programming and especially interfaces. I understand they are contracts and I understand how IEnumerable and IEnumerator work - or so I think. I've been reading this article on MSDN: IEnumerable Interface I understand how everything is set up. I'm a little unclear though in the Main loop

A followup to Does .NET JIT optimize empty loops away? : The following program just runs an empty loop a billion times and prints out the time to run. It takes 700 ms on my machine, and I'm curious if there's a way to get the jitter to optimize away the empty loop. using System; namespace ConsoleApplication1 { class Program { static void Main() { var start = DateTime.Now; for (var i = 0; i < 1000000000; i++) {} Console.WriteLine((DateTime.Now - start).TotalMilliseconds); } } } As far as I can tell the answer is no, but I don't know if there are hidden compiler options I might not have tried. I

How can I get the current CLR Runtime version in a running .NET program ? Laurent Etiemble Check out System.Environment.Version property ( http://msdn.microsoft.com/en-us/library/system.environment.version.aspx ). Since .NET 4.5 you can't really use System.Environment.Version (it will only return 4.0.{something}, allowing you to verify that you're "at least" on 4.0 but not telling you which actual version is available unless you can map a full list of build numbers in). Instead (as @jim-w mentioned) you have to check the registry against a "simple" lookup table. It's a bit ridiculous and being