Ok so this is probably best to explain using IL opcodes.
IL_0000: ldc.i4.s 0A
IL_0002: stloc.0 // n1
IL_0003: ldc.i4.s 14
IL_0005: stloc.1 // n2
The first 4 lines are kinda self explanatory ldc.i4 loads the variable (int of size 4) only the stack while stloc.* store the value at the top of the stack
IL_0006: ldloc.0 // n1
IL_0007: ldloc.1 // n2
IL_0008: stloc.0 // n1
IL_0009: stloc.1 // n2
These lines are essentially what you have described. Each values is loaded only the stack, n1 before n2 and then stored but with n1 being stored before n2 ( therefore swapping )
This I believe is the correct behaviour as described in the .NET specification.
mikez also added more detail and help me track down the answer but i believe the answer is really explained in 7.3.1
When an operand occurs between two operators with the same precedence, the associativity of the operators controls the order in which the operations are performed:
Except for the assignment operators and the null coalescing operator, all binary operators are left-associative, meaning that operations are performed from left to right. For example, x + y + z is evaluated as (x + y) + z.
The assignment operators, the null coalescing operator and the conditional operator (?:) are right-associative, meaning that operations are performed from right to left. For example, x = y = z is evaluated as x = (y = z).
Precedence and associativity can be controlled using parentheses. For example, x + y * z first multiplies y by z and then adds the result to x, but (x + y) * z first adds x and y and then multiplies the result by z.
What is important here is the order at which the operations are evaluated so what is actually being evaluated is
n2 = (n1) + ((n1=n2)*0)
where (n1) + (..) is evaluated left to right by being a binary operator.