CIRESON PLATFORM SDK TOOLS

The Cireson Platform SDK tools provide default templates for Platform functionality along with a toolbar of tools that make working with the platform easier. Below is a description of each toolbar button and what it is used for.

About Cireson About Cireson Platform

  • Shows current version available and the version installed in the current project

Remove Content Remove Content

  • Removes content root files from the instance of Platform designated by the Platform Api Url.

Upload Content Upload Content

  • Uploads the file changes to the Platform service web server
  • Platform Api Url
    • The URL to which the corresponding Platform service is listening
  • Auto Upload Saved Files
    • Uploads saved files automatically

Debug Extension Debug Extension

  • Debugs the instance of Platform designated by the Platform Api Url by attaching to the process shown in the Attach to Process field.
  • Skip Build
    • Skips the build before starting the debugging
  • Remote Debug
    • Allows for remote debugging.

Start Platform Service Start Platform Service

  • Starts an instance of the Platform service
  • Run Worker, Run Web Server, Use Basic Authentication
    • Feature options for this instance of the Platform service
  • Listener URL
    • The URL to which this instance of platform will be listening. Multiple instances of the platform must have a unique URL.
  • Specify Connection String
    • Check this box to customize the Database Connection String.
  • Platform Host Version
    • Allows the version of Platform to be selected. Check the Show Pre-Release box to select from release candidate versions.

Upload Platform Extension Upload Platform Extension

  • Compiles and uploads the file changes to the designated instance of the Platform Service
  • Platform Api Url
    • The URL to which the instance of Platform is listening.

Reference an assembly from a running platform instance Reference an assembly from a running platform instance

  • This dialog allows you to select an installed extension, and then select an assembly from that extension to allow you to develop against classes within the remote assembly without including it in your extension.
  • An example is with the Cireson PlatformCache product. Because the PlatformCache creates models based on the ServiceManager environment, the classes are potentially different between installations. For this reason if you would like to extend the functionality, you must create a reference to the dynamic classes while developing.