Skip to content

ASCOM Remote - Version 6.7.0+4779
Compare
Choose a tag to compare
@Peter-Simpson Peter-Simpson released this 29 May 13:03
· 85 commits to main since this release
v6.7.0+4779
142f7a8
This commit was signed with the committer’s verified signature. The key has expired.
Peter-Simpson Peter Simpson
GPG key ID: 11E6EAFE581B7600
Expired
Learn about vigilant mode.

The installer is located in the "Assets" section at the end of these release notes

Highlights and Dependencies

The Remote Server can now be configured to run as either a 32bit or a 64bit application. 64bit mode will primarily benefit 64bit capable in-process DLL camera drivers that deliver large images. Other devices are not expected to see significant benefits from 64bit operation.

Please note that drivers implemented as 32bit in-process DLLs will fail if loaded in the 64bit Remote Server application.

The other significant change is an infrastructural switch from .NET Framework to ,NET 7.0, which has enabled the introduction of SEMVER version numbers and alerts when application updates are available.

Remote Server Changes

  • The Remote Server can run as either a 32bit or a 64bit application. The start-up bitness is configured through the Setup dialogue.
  • When an application update is available, a button will appear on the main server form that will open a browser at the GitHub release page from which the update can be downloaded.
    • Update alerts are enabled by default and can be configured off, if required, in the Setup dialogue.
  • Remote Server configuration is now split onto two tabs in the Setup dialogue.
  • Version numbering has changed to SEMVER format.
  • The application is now implemented using .NET 7.0 rather than .NET Framework.

Bugs Fixed

  • ClientID and ClientTransactionID are now treated as optional parameters in line with the Alpaca specification.
  • CORS support now works with pre-flighted requests.

Alpaca API Reference Documentation Updates

  • Section 2.2.2 was clarified to address casing of boolean and string parameter values.
  • Section 2.3.1 was clarified to confirm that ‘thousands’ separators must not be used.
  • Section 2.7 was updated to note the requirement to set a Content-Type header on JSON responses.
  • Section 6 - Merged the ImageBytes specification into the API Reference.
  • Section 6.7.1 was clarified to indicate that none of the fields should return negative values.
  • Section 6.10 was updated to describe support functions in the cross platform ASCOM Library for .NET users as well as approaches available to users of other languages.
  • Added a “Client Considerations” section that includes the recommended approach for handling errors from Alpaca devices.

Installer SHAs

SHA256: 8106362dff83a5c1ee188048d1a68ab1b242bc440ae8288b5b87b1591a041c59
SHA1: 8fdeb32d2470c25411fdb5ffb3b13fcbfc8038ce

Assets 3
Loading