C#

Christian Graus wrote:

DateTime.Now creates a new value

.method private hidebysig static void Test2([out] valuetype [mscorlib]System.DateTime& abcd) cil managed
{
    .maxstack 8
    L_0000: nop 
    L_0001: ldarg.0 
    L_0002: call valuetype [mscorlib]System.DateTime [mscorlib]System.DateTime::get_Now()
    L_0007: stobj [mscorlib]System.DateTime
    L_000c: ret 
}

George_George wrote:

making a value copy from the new instance returned by DateTime.Now to another new instance, and making abcd pointing to the "another new instance".

George_George wrote:

Out variable saves value copy on stack if the value type is big.

void Method(int *p)
{
   int x = 20;
   *p = x;
}

void G()
{
   int y = 10;
   Method(&y); //out y
}

George_George wrote:

Sorry my English is not good. I think you mean out variable only affects function call behavior (passing pointer other than passing a value copy), not affecting assignment, correct?

George_George wrote:

no need to make another value copy from the instance created by DateTime.Now to another instance (and making abcd point to the "another instance")

willybt88 wrote:

to a running Winforms app (not in .NET)

willybt88 wrote:

I imagine that this is going to require ActiveX, can someone just confirm that this is the correct approach?

Christian Graus wrote:

..references to the .NET 3 dlls, and you just need to add those references.