There is not a one-to-one correspondence between every property, method, and event in Spread COM and every member in Spread.NET, but there are equivalents for many of the members. Spread.NET offers more features than Spread COM. Some functionality in COM has no corresponding functionality in .NET. The following tables are provided to help find an equivalent Spread.NET member for each Spread COM property, method, and event where there is one. If there is no equivalent, the table shows that. For more information on differences, refer to Differences in Behavior and Operation. If there are multiple equivalents, you should consult the Spread.NET documentation for more information about the different members to judge which is the best to use. This is not intended as a complete upgrade guide, but as a handy reference for finding equivalents for particular members.
Some equivalents require code to reproduce the Spread COM behavior. If the equivalent requires code, the table points you to sample code provided with Spread.NET. Properties with no equivalent are generally not imported when opening a Spread COM file in Spread.NET. For more information about how imports are handled, refer to Object Import from Spread COM.
These tables show the Spread.NET classes and members in a particular shorthand; for example "SheetView.BackColor." To use this class and member in code, you might write:
FpSpread1.Sheets(0).BackColor = Color.Navy
Alternatively, you might create a SheetView object and call it’s BackColor property. See the Spread.NET documentation for more information about working with Spread.NET.
Spread COM files that are imported into Spread.NET use some of these equivalents during import, depending on many factors. For more information about how Spread COM files are imported into Spread.NET, see Object Import from Spread COM.
The following topics provide detailed lists comparing members of Spread COM and members of Spread.NET:
