To access the new .NET components simply add a reference from the .NET tab. All components support Intellisense so overloads and paramater descriptions are available inside the Visual Studio IDE. The new component names are:
|ASCOM Astrometry||This includes 32/64bit versions of the original, optional NOVASCOM and Kepler components together with a full implementation of the USNO NOVAS v2 astrometry library and a new easy to use component from converting between J2000, apparent and topocentric co-ordinates. Version 126.96.36.199 and later also have a full implementation of NOVAS v3.|
|ASCOM Client Toolkit||The 1.0.5 version enables clients to use early and late binding drivers from Platform 5. Version 188.8.131.52 and later enables .NET clients to access drivers from Platform 5 and Platform 6 transparently, without regard for interface changes.|
|ASCOM Device Intrfaces||This provdes master device interface definitions for Platform 6 compliant drivers. .NET clients and drivers can use this directly or through the Client Toolkit, which provides a concrete implementation.|
|ASCOM Exceptions||The original exceptions have been extended to include specific InvalidValue and ValueNotSet exceptions so that applications can correctly interpret these states.|
|ASCOM Utilities||This is a single component, refactored from the Platform 5 driver helpers,that provides a range of helpful support functions. A few functions have been omitted as almost all programming languages provide these and it has been extended in a variaty of ways, see: Version 5.5|
|ASCOM Conrtols||This prodes a number of GUI components for use within Visual Studio to enhance the user visual experience of setup dialogues and handboxes.|
|ASCOM Attributes||This allows driver authors who are using C# local server template to mark assemblies as being served classes.|
The names above will appear on the Visual Studio Add Reference .NET tab, simply add these to your project to access to the new components. If you wish to develop a Platform 5 only client or driver, you should use the Master Interfaces definition from the COM components tab to access the device interface definitions. If you are developing to Platform 6 standards you should use the ASCOM DeviceInterfaces reference on the .NET tab.
Over time you should migrate away from the VB6 COM components to use the native .NET components to maximise the longevity of your drivers and applications. There is curently no "must do by" date in sight but a change to the Windows platform that renders the VB6 components unviable to repair could occur at any point in the future.
The same is the case for Platform 5 device interfaces; the Platform 6 interfaces are backwards compatible and offer sigificant extensibility benefits such as the Actions method.
Further information on capabilities is given in the namespace section and some code examples of using the new features are also provided.