On Windows OS, FeResPost is also distributed as a .NET assembly. Several characteristics of FeResPost as a .NET assembly are described in this Part.
In general, the class names, their methods and attributes (properties), the parameters of these methods and attributes are the same as those available in the FeResPost ruby extension. When necessary, modifications have been done in the ruby extension in order to maintain as much as possible the compatibility between the ruby extension and the .NET assembly. Therefore, the user is referred to Parts I, II, III and IV to find information on the use of the different classes and methods. In most cases, the information given there is sufficient to use the .NET assembly.
However, an exact match between the ruby extension and .NET assembly is not possible. The conventions that have been adopted are detailed below when incompatibility problems were not solved. More generally, the specific aspects are explained here of the use of FeResPost as a .NET assembly.
This Part of the document is organized as follows:
Chapter VIII.2 presents the .NET characteristics of the FeResPost generic classes described in Part I.
Chapter VIII.1 presents the .NET characteristics of the FeResPost CLA classes described in Part II.
Chapter VIII.3 presents the .NET characteristics of the FeResPost generic classes described in Part III. (Solver classes.)
Chapter IX.1 gives a few examples illustrating the use of FeResPost .NET assembly.
The installation of the .NET assembly is described in section X.A.4.6.
In the different sections of this chapter, the conventions that have been adopted when translating the ruby extension into a .NET assembly are explained. Information is given each time the ruby methods are modified to be implemented into the .NET assembly. For example, this is done for iterators, operators, “clone” method... Also, how objects are created with the assembly is explained.
Some differences between the .NET assembly and the ruby extension are highlighted below that are related to specific programmatic aspects of the two different systems.