Remote UI Limitations
The Object Navigator IDE extension runs its UI out-of-process (Visual Studio's Remote UI surface). Some WPF patterns simply don't transport across that boundary. This page is the authoritative "what works / what doesn't" list — each limitation has a documented, verified workaround.
| Pattern | Status | What's used instead |
|---|---|---|
DataGrid |
Doesn't transport reliably | A ListBox paired with a header Grid, everywhere a grid would normally appear. |
Horizontal ToolBar / ToolBarTray |
Doesn't work | A vertical StackPanel of buttons — see the 9-button toolbar on the Authoring page. |
SVG Path icon data |
Unreliable | Unicode emoji icons from a documented, verified icon set. |
| Drag-and-drop | Permanently deferred | An explicit two-step keyboard/menu workflow: "Arm for Scaffold" on the source, then "Drop Here" on the target. |
Why right-click, not a "⋯" menu
This is the same underlying constraint that shapes the Object Navigator's whole interaction model (see Authoring): right-click on a tree row is the only supported way to open a context menu — an overflow-glyph pattern was evaluated and explicitly ruled out because it doesn't hold up across the Remote UI process boundary.
These are concrete, verified facts about what the IDE's Remote UI surface can and cannot do reliably — not a wishlist. If a pattern above ever changes, it changes here first.