Status: Verified
GOAL:
How to deploy a GUI for .NET project
GOAL:
What files are needed at runtime by a GUI for .NET application, and where should they be placed?
GOAL:
How to run a GUI for .NET application outside of the OpenEdge Architect development environment
GOAL:
How to deploy a GUI for .NET application to a Client Networking license
GOAL:
What files and assemblies are needed on the target machine when deploying an application containing UltraControls?
GOAL:
What files and assemblies are needed on the target machine when deploying an application containing Infragistics controls?
FACT(s) (Environment):
Windows
OpenEdge 10.2x
FIX:
The following are a list of basic steps necessary to deploy a GUI for .NET application to a target machine running only one or more OpenEdge deployment licenses such as Client Networking. Additional steps or variations on these steps might be necessary for a particular application depending on its features.
Verify that the startup or main routine of the application is a procedure (.p) rather than a class (.cls). Class files (and r-code compiled from them) cannot be run directly from the command line or started from a desktop icon. The startup procedure should instantiate the class and run the instance. It should contain code similar to the following:
DEFINE VARIABLE MyMainClassInstance AS MyMainClass NO-UNDO.
MyMainClassInstance = NEW MyMainClass().
WAIT-FOR System.Windows.Forms.Application:Run(MyMainClassInstance).
Verify that Microsoft .NET Framework is installed on the production machine. .NET Framework 3.0 or higher is required; see OpenEdge Getting Started: Installation and Configuration, "Windows Installation Requirements > Required third-party applications" for the specific .NET Framework version required with your OpenEdge release. During the OpenEdge installation process, if only deployment products are being installed a check box option is provided to install the .NET Framework if needed. If OpenEdge has already been installed without the .NET Framework, the .NET Framework may be downloaded from the Progress Download Center or from Microsoft at http://msdn.microsoft.com/en-us/default.aspx.
OpenEdge 10.2B only: Verify that service pack 10.2B01 or later is applied. If it is not possible to apply a service pack, see P158659, ".NET form crashes when run with OpenEdge 10.2B deployment licenses only" for additional steps that are needed in this case.
Verify that any databases, AppServers, or other services needed by the application are installed and/or accessible.
Copy the following files from the OpenEdge Architect project directory (or other location) to the deployment directory structure of the target machine:
All .r files
Any .resx files that are used
Copy the following files from the OpenEdge Architect project directory (or other location) to the deployment directory structure of the target machine, or to a separate assemblies directory. If a separate assemblies directory is used, that directory must be specified at application startup with the -assemblies startup parameter.
assemblies.xml (This file will not exist if no external assemblies are used by the application.)
Any assemblies referenced by assemblies.xml that are not part of a product already installed on the target machine.
If a startup icon is desired on the target machine, create one as follows:
On the desktop, right-click and choose New > Shortcut.
Browse to <OpenEdge install directory>\bin\prowin32.exe. Click Next.
Type the name to display under th.e icon. Click Finish.
Right-click on the new icon and select Properties.
In the "Start in:" text box, type the full path of the desired working directory for the deployed application.
In the "Target:" text box, add any desired client startup parameters. If the -assemblies startup parameter is needed (see step 6), it should be included here. If the startup parameters are in a parameter file, just add -pf <path to parameter file>.
Click OK.
Once the startup icon has been created, it can be reused as long as the OpenEdge installation directory and application directory structure are in the same location on all target machines. The file will have the file name specified in step 7.3 and the file type ".lnk". Copy this file onto the desktop of each target machine instead of creating a new shortcut..