Studio Applications

Mercury-UI for ASP.NET contains the fully programmatic .NET assemblies, but the extent of its versatility does not stop there.

Included with the WebMenu and PanelBar components are the Studio design-time applications. These applications not only provide a visual design environment, they can also be used as stand-alone applications providing a straight-forward way for developers to prototype, implement and maintain their controls. You can even create static client-side DHTML for use in any HTML based project.

On-the-fly Preview Window
The on-the-fly preview window uses Microsoft Internet Explorer to perform the HTML rendering. The performance aspects of our component design makes it possible for us to instantaneously update the preview window whenever you make changes to the control.

State Files
The Studio applications can save control state in binary state files or XML state files which can then be loaded by the component running on the server, allowing even non-technical personnel to send changes to the site without editing code.

Source Code Generator
In addition to maintaining state files, the Studio applications can also generate server-side C#, VB.NET and C++/CLI source code that you can copy-and-paste into your projects for configuring the components.

Compile all DHTML into JavaScript (*.js) files
The Studio applications can stand on their own as useful web development tools with the ability to compile all of the generated client-side code into JavaScript files. These files can then be included in any web project, regardless of your web server choice. In one project, you might find yourself using the .NET assemblies to generate dynamic menus. In another project you may want to simply create static JavaScript files. Either way, it is covered with the Mercury-UI for ASP.NET.