Source Code Control: Managing Updates (Windows Embedded CE 6.0)
1/6/2010
This topic discusses how to manage installation of updates in a team development environment where source code control systems are used.
The purpose of updates is so that a team can obtain the latest operating system (OS) and board support package (BSP) patches from Microsoft and from their BSP vendors. For information about searching for QFEs for Windows Embedded CE 6.0, see CE Update Check Tool.
Best Practices
After obtaining a QFE, it is recommended that you install the QFE onto an integration machine, and then review any code changes that occur as a result of the installation. Then you should use the integration machine to build several run-time images that you can use to test for any issues related to regressions.
After you have completed this, you can make the decision whether to accept the QFE for use in your development environment. If the QFE is accepted, check the QFE into the source code control database.
Installation of QFEs typically overwrites any changes that a team might have made to Microsoft source code. To assist in avoiding this scenario and make sure that changes like these are not lost, you must use Catalog item cloning, which is functionality that was implemented in Windows CE 5.0 and later. For more information, see Cloning a Catalog Item.
Also, DIRS files might require merging. To assist in this process, CE 6.0 includes new functionality where you can choose to build all the subdirectories of a selected directory by using the following code in the directory's DIRS file.
DIRS=*
For more information, see Dirs File.