TABLE OF CONTENTS
Overview
When first installing the CadActive Creo application, there is an important question to consider first: How do we want to handle updates? We are continuously releasing new versions of the CadActive application with new functionality and bug fixes, so having a strategy around how to deploy those to a team of engineers is important. There are two different ways to install the CadActive application and both have vastly different steps to complete an update. Deciding on an update strategy informs the decision on how to install the CadActive application.
Installation options for the CadActive application:
- Directly installing a specific version. This option makes the update process slightly more complex, but is the preferred method for insuring that an entire team of engineers are working on the same release of the software.
- Using the CadActive Launcher to manage updates.
- Click here to find more information about installing the CadActive Launcher.
Step-By-Step
- First email support@cadactive.com to obtain the proper version of the app
- We will need to know what datecode of Creo Parametric you are running as we build our app for every supported version
- Once you receive the zip folder, copy the entire contents of the vX.X.X.X folder (there should be a bin folder, a text folder, and a cadactive.dat file)
- Navigate to the Local AppData directory (typically C:\Users\<username>\AppData\Local), create a new folder, and name it CadActive
- Inside of the CadActive folder, create another folder called cadactive-creo
- Inside of the newly created CadActive folder, paste all of the contents copied earlier
- At this point, the CadActive application is fully installed
- The final step is to set up the config.pro file to run the launcher when Creo starts up (more information can be found here)
If you need additional support with installing the CadActive application, please email support@cadactive.com
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article