.NET Objects (Magic xpa 4.x)
In Online tasks, when leaving a task running in a subform and entering this task again, all the variables are initiated. .NET variables not attached to a .NET control behave in the same way.
.NET variables attached to .NET controls are not initiated and keep their .NET object, so you do not need to set their properties again.
.NET objects are automatically disposed when the Runtime engine is closed.
When using .NET objects in Batch tasks on the server or when running from the Studio, the Runtime engine is not closed and, therefore, the .NET objects are not disposed.
If you want to dispose them, you can use the Dispose method of the .NET object.
For example: Evaluate var.Dispose() with CND='Not IsNull(var)'
|
|
-
If you have two .NET objects, and you use the Magic xpa Update operation to update one variable with another, you are not creating a copy of the .NET object as you would expect. Because both variables have the same reference, this means that any changes made to the properties of one variable are reflected in the second variable, since they are the same object.
-
The same .NET object can be referenced from a Rich Client task and a non-interactive Rich Client task.
-
It is not possible to use the same object in a Rich Client task and a Batch task (unlike Online).
|
.NET Variables vs .NET Objects
How Do I Get the Value of the Property of a .NET Object?
