Zenzel UI DesignerDesign Windows Forms, WinUI/UWP, and .NET MAUI interfaces visually without leaving Visual Studio Code. Zenzel UI Designer provides a familiar design surface with a framework-aware Toolbox, Document Outline, Properties and Events, component tray, layout tools, preview rendering, undo/redo, and safe source generation. Highlights
Supported designers
Windows Forms and WinUI/UWP target Windows. MAUI preview capabilities depend on the SDKs and target platforms installed on your system. Get started
To start a new interface, run Zenzel UI Designer: Create Document from the Command Palette. The command can create Windows Forms, WinUI 3, UWP, or .NET MAUI documents with their required companion files. Existing files are not overwritten. Toolbox and child controlsThe Activity Bar Toolbox is shared by every designer. It switches automatically between WinForms, WinUI/UWP, and MAUI controls and includes compatible project controls discovered in the active workspace. Select a container before choosing a Toolbox item to add the new control as its child. You can also drag a control directly onto a compatible container or change its parent through Properties. Invalid and cyclic parent relationships are rejected. Nested hierarchies are shown in Document Outline and preserved when saving or duplicating a container. Properties and eventsSelect a control on the surface or in Document Outline, then use the Activity Bar Properties view:
Automatic sizing is used unless Stretch/Fill or a fixed dimension is explicitly selected. The designer supports MAUI When an event handler does not exist, the designer adds a handler stub to the companion partial class. If a XAML code-behind file is missing, it is created automatically. Existing handler implementations are never replaced. Design surfaceStandard controls receive framework-specific design-time previews, including buttons, toggle buttons, switches, check boxes, radio buttons, text inputs, lists, trees, data grids, calendars, navigation, menus, media, charts, dialogs, shapes, and layout containers. Stateful controls reflect properties such as Custom controls use a recognized base-control preview when possible. If a native or vendor renderer is unavailable, the control remains visible and editable through a clearly labeled placeholder instead of causing the designer to fail. Non-visual Windows Forms items—such as timers, dialogs, image lists, and data components—appear in the component tray beneath the design surface. Useful shortcuts
Safety and diagnosticsYour source remains authoritative. If the designer encounters markup, bindings, serializers, or code that it cannot safely reproduce, it enters read-only safety mode and explains the problem instead of partially rewriting the file. Parsing and rendering failures appear in the Problems view and on a recoverable designer error page. Source files remain unchanged when an operation fails. Project-control discovery can inspect compiled metadata in a trusted workspace. The designer reads property and event metadata without constructing project controls or running application code. Settings
Preview noteThe portable preview is a design-time representation. Runtime-only behavior, platform services, complex bindings, external resources, and vendor-specific native rendering may still require running the target application. Support the projectUse the Donate button in the designer toolbar to support Zenzel UI Designer through Venmo. Repository: https://github.com/czenzel/vscode-zenzel-ui-designer |