Do I need to use version control when using MPLAB Harmony?

No, but using version control is strongly advised for any embedded development project. It is especially important with an MPLAB Harmony project because the MPLAB Harmony Configurator (MHC) generates code which is merged with the user's existing project. Done right, this merge won't adversely affect the user project, but if mistakes are made in the merge, it can be hard to recover without version control.

The level of version control used depends on the needs of the user. Users who modify the underlying framework or board support package (bsp) may want to place the whole Harmony installation under version control. Users who only have modifications to their project under the apps folder may only need to place their project (apps/myproject) under version control, as long as they remember which version of Harmony corresponds to their source.

If you really don't want to use a version control system, the local history built into the MPLAB X IDE may be able to help.

© 2017 Microchip Technology, Inc.
Information contained on this site regarding device applications and the like is provided only for your convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with your specifications. MICROCHIP MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY OR OTHERWISE, RELATED TO THE INFORMATION, INCLUDING BUT NOT LIMITED TO ITS CONDITION, QUALITY, PERFORMANCE, MERCHANTABILITY OR FITNESS FOR PURPOSE. Microchip disclaims all liability arising from this information and its use. Use of Microchip devices in life support and/or safety applications is entirely at the buyer's risk, and the buyer agrees to defend, indemnify and hold harmless Microchip from any and all damages, claims, suits, or expenses resulting from such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual property rights.