Difference between revisions of "Deployment"
m |
m |
||
| Line 13: | Line 13: | ||
- Creating a backup of your project<br> | - Creating a backup of your project<br> | ||
- Complying with the license by ensuring the next user has the complete solution<br> | - Complying with the license by ensuring the next user has the complete solution<br> | ||
| − | - Knowing that you will have the latest version of the source<br> | + | - Knowing that you will have the latest version of the source that matches the executable<br> |
Latest revision as of 06:38, 30 January 2019
AVOID USING THE "PUBLISH" FUNCTION
Publish has a few quirks that are sure to eventually get you into trouble. It is HIGHLY recommended to never use Publish.
The simplest technique for deployment is commonly referred to as XCOPY deployment. An application built using the >NET framework does not require a complicated installation with copying files all over the hard disk. Applications are generally self contained with all of its supporting components within the same directory.
The recommended practice for deployment is to copy the complete solution to the target machine and create a shortcut to AdvancedHMI\bin\debug\AdvancedHMI.exe
The complete solution includes all 4 directories and contents( AdvancedHMI, AdvancedHMIControls, AdvancedHMIDrivers, AdvancedHMIcs). By copying the complete solution you are doing multiple things:
- Creating a backup of your project
- Complying with the license by ensuring the next user has the complete solution
- Knowing that you will have the latest version of the source that matches the executable
