interoperability
The ability of separate systems, libraries or code written in different languages to work together.
In more detail
Boundaries with outside code often need special handling, because that code does not follow your platform's conventions, for example when .NET calls a native C library or React drives a third-party chart widget. Keep such boundaries narrow and documented.
Example
.NET: analyzer exceptions at a native interop boundaryRelated terms
- suppression — Marking one diagnostic or scanner finding as intentionally ignored for some code, usually with an inline comment or attribute and a reason.
- Roslyn analyzer — A plug-in to the C# compiler that inspects code while you edit and build, and reports diagnostics about likely bugs, unsafe patterns or style.
- native event — The original event object created by the browser, which React wraps in a SyntheticEvent.
- ref — A React handle that points at a real DOM element, so code can focus it, measure it or attach listeners.
- external system — Anything outside React that a component must stay in step with, such as the network, a timer, a browser API, a chat server or a non-React library.
Taught in
- Code Quality: .editorconfig and Roslyn Analyzers — Modern .NET Core, C# & Enterprise Microservices
- SyntheticEvent System: Event Delegation in Modern React — React 19 & Modern Component Architecture