Echelon LNS - Manual (Page 32)

LNS Programmer's Guide 18
collection. You may not want the application to copy every extension record
stored in the object. You can use this property to mark which extension records
the application should copy.
• The ConstNodeConnChangeEvent event now returns additional values.
Previously, the possible values that could be returned for the event’s
ObjectChangeType element were contained in the ConstObjectChangeTypes
constant. Those values are now stored in the ConstNodeConnChangeType
constant, which includes more detailed information. The values of the
ConstNodeConnChangeTypes constant now map to the values of the
ConstObjectChangeTypes constant, so this change will not affect applications
that were written using pre-Turbo Edition versions of LNS.
• The ItemByProgrammaticName() method has been added to the
LonMarkObjects and NetworkVariables collections. This allows you to
retrieve a LonMarkObject or NetworkVariable from its respective collection
by its programmatic name.
• The AliasUseCount and AliasCapacity properties have been added to the
AppDevice object. These properties indicate how many aliases are being used on
a device, and how many are available, respectively.
• You can now use the OnSessionChangeEvent event to keep track of when the
Network Service Device is offline. You will need to know this because polling is
suspended and monitor and control events will not be delivered to your
application while the Network Service Device is offline. Once your application
registers for this event, is will be fired each time the state of your client’s
Network Service Device changes from the online state to the offline state, or vice
versa.
New LNS Runtime Installations
The LNS Server and LNS Remote Client installations, which are created and installed
with the LNS Redistribution Kit, have been re-created as Windows Installer (a.k.a.
Microsoft Installer) installations in order to make LNS Turbo Edition installations more
compatible with recent versions of Windows. This has important implications for how
the LNS redistribution installations should be installed. For more information, please
see Chapter 14, Distributing LNS Applications.
Compatibility
Echelon's goal is to allow easy integration of new LNS releases into your LNS
applications. COM interface compatibility allows for the possibility of “drop in”
replacement of one LNS release with another, and Echelon strives to design new features
and fix defects in a way that supports this. The following sections provide details on
several LNS compatibility issues you should consider when upgrading to LNS Turbo
Edition. Some of these issues are applicable to all LNS releases, and some apply
specifically to LNS Turbo Edition.