Yes, this is very similar to Tuple from .NET 4.0, but goes back to .NET 1.0 and ASP.NET 1.0 in particular. It is mainly used in Serializing ViewState :
The page class contains SavePageViewState() , which is called during the state phase of the page lifecycle state. The SavePageViewState() method begins by creating a Triplet , which contains the following three elements:
- The hash code of the page. This hash code is used to ensure that the state of the view has not been # redirected between postbacks. Weβll talk more about state hashing state in the State and Security State section.
- State of collective representation of the hierarchy
Page . ArrayList of controls in the control hierarchy that must be explicitly called by the page class during the lifecycle postback event retry phase.
There is also his "little brother" called Pair .
There is absolutely no reason why you should even worry about these classes, otherwise an unholy, untyped mess will occur.
source share