BeepService initialization

Bootstrapping IDMEEditor and wiring connections in desktop apps. Full detail: BeepDM/.cursor/beepservice/SKILL.md; modern registration: beepserviceregistration.

Typical flow

  1. Create or obtain the editor (e.g. DMEEditor or hosted BeepDesktopServices).
  2. Build ConnectionProperties and persist via ConfigEditor.
  3. Open the datasource; verify ConnectionState.Open.
  4. Run migrations or schema setup as required.

Pitfalls

  • Do not call GetDataSource before a successful open.
  • Reuse a shared editor instance across forms.
  • Surface migration errors instead of swallowing them.

Plugin documentation in this repo

After the editor is up, per-datasource behavior is described under Data providers. SaaS REST command references: flagship conn-* index (REST overview).

Editor ConfigEditor