NOTE>>>> WE need to have a smaller number of KEY CONCETS, 2 to 4 tops. Move the other other parts. We must organization to QUICKLY explain how to run the base, then later in the section more length dexcript
this some text that cab be merged is this chapter.
You do not need to open the configuration tools, Project Designer, to run the project,. You can run directly by using the Project Management tool.
When deploying your Project in product in its final location, you can setup automated procedures to start the execution, as described in Deploying the Application.
This manual section will focus on Starting the Project execution from within the Project Designer, as it is typical to do during the development and test phase of the project.
To start the Project is production mode,
- Go to Run → Startup
- Click the Run Startup button
There are a few customizations you can do on how the project shall be executed, such as if the project will run in your local computer or start in a remote Server computer, which modules will be loaded, and some other settings described in this section.
Startup Computer
| Run | Startup Computer options | |
|---|---|
| Field | Description |
| Local | The TStartup (project ) is launched locally on the local PC |
| ProjectServer | The TStartup (project) is launched on a connected Server PC. This option is only enabled if the project was opened from a remote ProjectServer. |
On Run → Modules, you should see two options regarding the displays affected by this setting:
- If Displays is selected - A RichClient is opened on the project server when the project is started
- If LocalDisplays is selected - A RichClient is opened on local PC when the project is started
Startup Settings | |
|---|---|
Field | Description |
UserName | Enter a valid username to access the application. |
Password | Enter the password that corresponds to the username. |
Project Server | Read-only. Displays the IP address or the name of the computer where the project is, which is based on the configuration in the Server tab. |
Port | Displays the port that FactoryStudio uses for access. For test, it uses 3201. For startup, it uses 3101. These ports must be open on the server. |
PortWA | Displays the port that FactoryStudio uses for access with Windows Authentication. For test, it uses 3202. For startup, it uses 3102. These ports must be open on the server. |
Use only Windows Authentication | Checks if the system can only accept Windows Authentication. |
Startup Computer | Read-only. Displays whether or not the configured server is the local computer or a remote server. |
Execution Path | Overrides the default execution path, which is the project file location. |
Module Information | Runs the Module Information tool. |
Property Watch | Runs the Property Watch tool. |
Trace Window | Runs the TraceWindow tool. |
Run Modules | Select which modules are executed when running the project. |
Status | Shows the current status of running, connected, or disconnected.
|
Enable Online Configuration | Select in order to your changes to immediately apply to the test runtime. You must also be connected to the running project (see status setting above). |
You can use Enable Online Configuration to apply changes in real-time. All changes must be saved before they can appear on a screen.
Having supported projects that run in Linux environments for years, we continue to make improvements to ensure your project experience in the Linux environment will be as close to the .NET experience as you can get.
You can design your projects once and ensure your end users will get the same experience regardless of which platform they use.
If opening a ProjectServer from a Linux computer, all described procedure are the same, whatever the remote computer is Windows or Linux.
For information of specific Linux Platforms, refer to the Linux Platform documentation.
In this section...