Project File Maintenance (Windows CE 5.0)
If you work in a group, typically you want to share the Platform Builder project (.pbpxml) file for a workspace with other group members.
This ensures that everyone in the group can build the projects that are defined in the workspace by using the same files, settings, and tools; and ensures that everyone gets the changes to the .pbp file and builds with the most current settings.
Updating the .pbpxml file in a group setting requires some coordination among group members for the process to work. In the optimal case, all group members get the file from the source code control system when they open the project, but no one checks it out. This keeps the file available for access by other group members.
The source code control system prompts you to check out the .pbpxml file whenever it has determined that changes are necessary. However, you must remember to check the file in again and notify the members of the group that it has changed.
At this point, other members of the group need to close the workspace and then reopen it to get the new version of the .pbpxml file.
If they have set the option to prompt to get the latest versions of files, opening the workspace reminds them to get the latest version.
If two or more members of the group simultaneously check out the .pbpxml file and revise it, checking the file in could require merging changes.
Because the source code control system might write multiple settings to a single line of the .pbpxml file, and changes to settings by different users might alter a single line in two or more different places, reconciling those changes manually could result in errors.
If your source code control system supports exclusive checkouts, check out the .pbpxml file for exclusive use when you need to alter it.
See Also
Send Feedback on this topic to the authors