Game Development Reference
In-Depth Information
So you now have the code and can browse through it at your leisure and start
making your plans to take over the world. Ahem, maybe that's just me!
As a
big
tip, if you are using
Visual Studio
to view the code, then I highly
recommend downloading the
VisualHG
extension (
Tools
|
Extensions
and
Updates
) and then setting the source control manager for the project
(
Tools
|
Options
|
Source Control
) to
VisualHG
. You will then see a
graphically enhanced
Solution Explorer
and see the change state of each
file. This gives you direct access to any modification/changes to source
from within
Visual Studio
!
Keeping up to date
Over time with each new release Unity will be updating the source repository on
BitBucket with changes and fixes, so you need to ensure you keep up to date.
When a new release is announced, be sure to pop over to your repository on the
BitBucket website and use the
Sync
feature that will appear in the top-right hand
corner of the page. This will automatically get any new changes and attempt to
merge them into your own project. Then you will need to refresh your local code via
your source control application so that you are now working with the latest source.
Be sure to check if any changes you are working on are affected by the
Unity changes by updating any separate develop branches you have as
well as by refreshing them. Each is a separate project in its own right.
If however, you have not created your own fork/copy, simply update/refresh your
local Mercurial repository using your source control application to continue.
One great thing about the source being public is that you have more detailed
information about what has changed in a file-by-file, line-by-line comparison
between releases. The easiest way to see this is via the commit entries for the project.
