ManagedCode.Communication

Trigger On

• integrating ManagedCode.Communication into services or APIs
• replacing exception-driven result handling with explicit results
• reviewing service boundaries that return success or failure payloads
• documenting result-pattern usage across ASP.NET Core or application services
• mapping application errors to RFC 7807 problem details, Minimal API results, SignalR filters, or Orleans call filters

Workflow

1. Confirm the boundary where the library belongs:

- service result contracts - application manager boundaries - API endpoints that translate results into HTTP responses

1. Keep result creation and error mapping explicit instead of mixing exceptions, nulls, and ad-hoc tuples.
2. Pattern-match result objects at the boundary that converts them into user-facing responses.
3. Do not hide domain failures behind generic success wrappers.
4. Configure framework integration only where it removes manual translation:

- ConfigureCommunication() for ASP.NET Core logging and converters - WithCommunicationResults() for Minimal API endpoint or group conversion - Orleans or SignalR packages only when those runtime filters are actually in use

1. Validate positive, negative, and error-path handling after integration.

flowchart LR
  A["Domain or service operation"] --> B["ManagedCode.Communication result"]
  B --> C["Application or API boundary"]
  C --> D["HTTP response or caller-visible contract"]

Deliver

• guidance on where explicit result objects improve clarity
• usage boundaries for translating results into API or caller responses
• validation expectations for success and failure flows
• package and integration choices for the actual runtime boundary

Validate

• result handling is consistent across the boundary that uses the library
• callers do not fall back to exception-only logic for normal failure cases
• negative and error scenarios are documented and tested
• Minimal API endpoints return expected success and RFC 7807 failure shapes
• pagination metadata is stable when CollectionResult<T> is used
• Orleans or SignalR integration is covered by runtime-level tests when those packages are installed

Related skills