Visual WebGui deployment can be done simply by copying the project directory without the source files with copy paste to the a virtual IIS directory or you can use the Microsoft web application setup project and use it exactly as you would create an ASP.NET installation. A Visual WebGui project is actually an ASP.NET project with extra references.

Visual WebGui requires IIS installed and .NET1.1 or .NET2.0 installed. You also need to install a new ".wgx" script map in the IIS with the same definitions as the ".aspx" script map but you should remove the "check file exist" checkbox as Visual WebGui uses virtual pages.

Developing a Visual WebGui application requires IIS installed ,.NET1.1 or .NET2.0 installed and Visual Studio 2003 or Visual Studio 2005. You also need to install a new ".wgx" script map in the IIS with the same definitions as the ".aspx" script map but you should remove the "check file exist" checkbox as Visual WebGui uses virtual pages. The .NET2.0 / Visual Studio 2005 version also needs Microsoft's update for Visual Studio 2005 web applications that can be found here (http://msdn.microsoft.

Make sure that you have followed the following guide lines: You have registered the ".wgx" script map / You have remembered to uncheck the check file exist check box in the script map definition dialog / You are running a valid virtual ".wgx" page.

Visual WebGui is actually WinForms for web meaning that you have classes that represent windows instead of pages you would normally see in a web application. While in WinForms you would use a static main method that runs your root form class, Visual WebGui can have many roots by mapping root classes to virtual pages. Mapping a virtual page to a Visual WebGui window is done through the "web.config" in the "Applications" section of the Visual WebGui configuration.

The Visual WebGui sources enable you to create new SDK objects or modify existing ones. It also enables you to create themes which are assemblies that embed resources that can override the default resources. Using themes you can create a totally different look and feel for an application. Already used in some production sites, themes are an excellent way to create applications that require a specific look and feel rather than the default XP look.

The Visual WebGui site can be a found here (http://www.visualwebgui.com) or you can see Guy Peled's blog which has further information and announcements here (http://www.geekswithblogs.com/gizmox ).

After you create a new user control and design it using the Visual WebGui designer you can add it to a form by placing a "Panel" control on a the design surface and by hand coding changing the type of the added panel control to the type of the created user control. You need to replace both the declaration and the initialization type of the "Panel".

You can find a simple class browser application that includes source code here (http://www.visualwebgui.com/Technology/Demos/tabid/117/Default.aspx). You can find an open source web implementation of Microsoft SQL enterprise manager application for multiple database types here (http://sourceforge.net/projects/vwg-ent-man).

Mainsoft for Java EE generates a script that you can use to run your console application outside your development environment.

We found the question of installation so troublesome with mismatch of versions and users patially installing the software we bundle the complete java jvm and libraries (including J3D?) and in a subdirectory of our installation directory. No troubles since we did that. Topic Java3DFAQ .

The Visual WebGui SDK is all a developer needs to develop a Visual WebGui application including design time assemblies. The Visual WebGui SDK includes the Visual WebGui personal server enabling developers to test thier application on their development station.

The Visual WebGui Server is all that is needed to deploy a Visual WebGui application including runtime-only assemblies. Normally, you will deploy a Visual WebGui application without the Visual WebGui runtime assemblies and install the runtime assemblies through the Visual WebGui Server installation. This enables the Visual WebGui runtime assemblies to be upgraded without reinstalling the Visual WebGui applications.

Open the IIS mmc admin and right click properties on the "Default Web Site" node. Select the home directory tab. Press on the configuration button. Double click the ".aspx" script map and copy the executable path (through the text box context menu as key commands do work). Close the ".aspx" definitions and press the add button. Paste the path into the empty executable text box and uncheck the file exist checkbox. Type in ".wgx" in the extension text box. Keep the all verbs radio button selected.

Yes, you can adapt the Java EE application you've developed to any standards-compliant Java EE application server such as JBoss or WebLogic. You will have to modify the generated server specific deployment descriptors and potentially change your code if you make direct calls to server-specific APIs or server specific extensions. With Mainsoft for Java EE, Portal Edition, the .NET Framework provided by Mainsoft is based on the JSR 168 specifications. Therefore, if you use the .

IT Works® ManagER is the primary interface used by the network administrator. Open the Help Desk panel of IT Works® ManagER, right click on a computer, drag the software package(s) to the desired computer and select Deploy. Sit back and relax. In minutes the software will be deployed to the selected computer or groups of computers.

Yes. Applications developed with the Enterprise or Portal Editions can be deployed in a clustered environment. If you are using Grasshopper, you can deploy to Tomcat only in a single CPU, non-clustered server. The Mainsoft for Java EE runtime libraries consist of JAR files that are compliant with the Java specification. These files can either be added to the classpath of the Java EE application server, or they can be included in the WAR file of the application being deployed.

ParaWeb automatically reads any application developed by ParaGrafix, so you can use application files developed for desktop Frontline with little or no modification. All you need to do is write some HTML pages with input forms, some output HTML templates, and a simple script detailing what output (DXF, GIF files, etc. ) should be generated. To see examples of HTML pages interacting with ParaWeb, click here

Build your application into a *.war file and deploy that file on your web application server. The uitest.war file that comes with the AppProjector download is an example of such a deployable application.