• Replies 3 replies
  • Subscribers 583 subscribers
  • Views 373 views
  • Users 0 members are here
Options
Related

Citect 2018 Deployment

kevin

Hello,


I'm finishing the development of my standalone application and now I want to transfer my project to the customer's pc.
My aim is do the transfer, avoiding that the client can read/modify the source code.
How can I do that?
Can I just backup the project from my PC and restore that in the new PC and delete only the Citect Editor?
Do I have to do the deployment activity?
What are the differences?


Thank you

  • I think you should just be able to copy the runtime, compiled files into the user folder. Rdb, ctg,... Easiest way is probably to note the time, compile you project, then go into the main project directory and sort by date modified. Then grab all the files modified after the time you noted. If you do it this way, make sure you turn incremental compile OFF. I'm fairly sure the compiled files are only stored in the main project, but if you have include projects, you might want to check those don't contain compiled files as well.

  • This will not work. Runtime uses more than only the RDB files. It also needs all CTF files and probably several DBFs as well.
  • It depends on how sure you need to be that the customer can't edit your project...

    If you want to be able to edit and debug the project yourself on their server, then do a full installation and put your full project on there. Then, delete the shortcut to the Citect Studio from the Start menu. You can run the studio manually using Windows Explorer.

    If you want to eliminate the Citect Studio from the server, you could choose Runtime-Only Server (or Runtime Only Client) installation when you install Citect on the customer's computer. Then, restore your project. They will have the full project, but they can only make changes and recompile if they figure out how to install the full version of Citect off the install CD.

    If you're concerned about someone stealing your proprietary code or trying to hack the project, you would have to give them only the compiled runtime files, not the full project, as was mentioned. The exact files needed may vary depending on the version of Citect and the features used. What you could do is set up a client using the [CTEdit]Copy parameter (check the documentation). Then, run the project on the client and open each page in the runtime (if you forget any, the client won't download those pages). The client will download all the necessary files from the copy path (full project) and store them in the local User folder (run path). You can then save your project folder(s) from the User folder as your runtime-only project to give to the customer.
© 2025 AVEVA Group Limited or its subsidiaries. All Rights Reserved.