How C# compiles and runs on CLR - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a simple C# class.

C Sharp (C#)

public class [1] {
    public int Number { get; set; }
}

Drag options to blanks, or click blank then click option'

AMyClass

Bvoid

Cint

DMain

Attempts:

3 left

💡 Hint

Common Mistakes

Using a keyword like 'void' as a class name.

Using a data type like 'int' as a class name.

The class name should be a valid identifier like MyClass. Keywords like void or types like int cannot be used as class names.

2fill in blank

medium

Complete the code to compile C# source into an intermediate language.

C Sharp (C#)

// The C# compiler converts source code into [1] code.

Drag options to blanks, or click blank then click option'

Aassembly

Bmachine

Cintermediate language

Dbyte

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing intermediate language with machine code.

Thinking the compiler produces assembly code directly.

C# source code is compiled into Intermediate Language (IL), which is CPU-independent code executed by the CLR.

3fill in blank

hard

Fix the error in the statement about CLR execution.

C Sharp (C#)

The CLR executes [1] code directly on the CPU.

Drag options to blanks, or click blank then click option'

Amachine

Bintermediate language

Csource

Dbyte

Attempts:

3 left

💡 Hint

Common Mistakes

Thinking CLR runs intermediate language code directly.

Confusing source code with executable code.

The CLR executes machine code, which is generated by just-in-time (JIT) compilation from intermediate language code.

4fill in blank

hard

Fill both blanks to describe the compilation and execution process.

C Sharp (C#)

C# source code is compiled into [1] code, which the CLR then [2] into machine code at runtime.

Drag options to blanks, or click blank then click option'

Aintermediate language

Binterprets

Cjust-in-time compiles

Dbyte

Attempts:

3 left

💡 Hint

Common Mistakes

Saying CLR interprets IL instead of compiling it.

Confusing intermediate language with byte code.

The C# compiler produces intermediate language code. The CLR uses just-in-time (JIT) compilation to convert this IL into machine code when the program runs.

5fill in blank

hard

Fill all three blanks to complete the explanation of C# execution on CLR.

C Sharp (C#)

The C# compiler generates [1] code, which is stored in [2] files. At runtime, the CLR uses [3] compilation to convert this code into machine instructions.

Drag options to blanks, or click blank then click option'

Aintermediate language

Bassembly

Cjust-in-time

Dexecutable

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing assembly files with executable files.

Thinking the compiler produces machine code directly.

C# source is compiled into intermediate language code stored in assembly files (DLL or EXE). The CLR uses just-in-time compilation to convert IL to machine code when running the program.

Practice

1. What is the first step when you compile a C# program?

easy

A. The C# code is converted into Java bytecode.

B. The C# code is converted into Intermediate Language (IL) code.

C. The CLR executes the C# code line by line.

D. The C# code is directly converted into machine code.

Solution

1. Step 1: Understand C# compilation process

   C# source code is first compiled into Intermediate Language (IL), not directly into machine code.

2. Step 2: Identify the role of CLR

   The CLR later converts IL to machine code at runtime, not during compilation.

3. Final Answer:

   The C# code is converted into Intermediate Language (IL) code. -> Option B

4. Quick Check:

   C# compiles to IL first [OK]

Hint: Remember: C# compiles to IL before machine code [OK]

Common Mistakes:

• Thinking C# compiles directly to machine code
• Confusing CLR execution with compilation
• Assuming C# compiles to Java bytecode

2. Which of the following is the correct syntax to compile a C# file named Program.cs using the command line?

easy

A. csc Program.cs

B. compile Program.cs

C. dotnet run Program.cs

D. gcc Program.cs

Solution

1. Step 1: Identify the C# compiler command

   The C# compiler command is csc, used to compile C# source files.

2. Step 2: Check other options

   compile and gcc are not C# commands; dotnet run runs projects, not single files.

3. Final Answer:

   csc Program.cs -> Option A

4. Quick Check:

   Use csc to compile C# files [OK]

Hint: Use 'csc' to compile C# files on command line [OK]

Common Mistakes:

• Using gcc which is for C/C++
• Using 'compile' which is not a command
• Confusing 'dotnet run' with compile command

3. Consider this C# program:

class Program {
  static void Main() {
    System.Console.WriteLine("Hello World");
  }
}

What happens when you run this program on the CLR?

medium

A. The CLR interprets the C# source code directly and prints 'Hello World'.

B. The program throws a runtime error because IL is missing.

C. The CLR converts IL to machine code and prints 'Hello World'.

D. The program compiles to Java bytecode and runs on JVM.

Solution

1. Step 1: Understand CLR execution

   The CLR runs the Intermediate Language (IL) by converting it to machine code just before execution.

2. Step 2: Confirm program output

   The program prints 'Hello World' after the CLR converts IL to machine code and runs it.

3. Final Answer:

   The CLR converts IL to machine code and prints 'Hello World'. -> Option C

4. Quick Check:

   CLR runs IL by converting to machine code [OK]

Hint: CLR converts IL to machine code before running [OK]

Common Mistakes:

• Thinking CLR interprets C# source directly
• Assuming runtime error without IL
• Confusing CLR with JVM

4. You wrote a C# program and compiled it, but when running it on a different computer, it fails. What could be a likely cause related to CLR?

medium

A. The program was compiled directly to machine code.

B. The source code was not saved properly.

C. The C# compiler was not installed on the target computer.

D. The target computer does not have the correct version of the CLR installed.

Solution

1. Step 1: Understand CLR dependency

   C# programs require the CLR on the target machine to run the IL code.

2. Step 2: Identify the cause of failure

   If the target computer lacks the correct CLR version, the program cannot run properly.

3. Final Answer:

   The target computer does not have the correct version of the CLR installed. -> Option D

4. Quick Check:

   CLR must be present on target machine [OK]

Hint: Check CLR version on target machine if program fails [OK]

Common Mistakes:

• Assuming source code affects runtime on other machines
• Thinking compiler must be on target machine
• Believing program compiles directly to machine code

5. You want your C# program to run on different operating systems without recompiling. How does the CLR help achieve this?

hard

A. By compiling C# code into platform-independent Intermediate Language (IL) and using Just-In-Time compilation on each OS.

B. By compiling C# code directly into machine code for each OS at compile time.

C. By interpreting C# source code directly on each OS without compilation.

D. By converting C# code into Java bytecode to run on JVM.

Solution

1. Step 1: Understand platform independence of IL

   C# compiles to IL, which is platform-independent and not tied to any OS.

2. Step 2: Role of CLR's Just-In-Time compilation

   The CLR converts IL to machine code specific to the OS and hardware at runtime, enabling cross-platform support.

3. Final Answer:

   By compiling C# code into platform-independent Intermediate Language (IL) and using Just-In-Time compilation on each OS. -> Option A

4. Quick Check:

   IL + JIT compilation = cross-platform support [OK]

Hint: IL plus JIT lets C# run anywhere CLR exists [OK]

Common Mistakes:

• Thinking C# compiles directly to machine code for each OS
• Assuming C# is interpreted without compilation
• Confusing CLR with JVM