In the Docs folder there is a file called Instructions, I suggest a good read of them to anyone who uses the app. Anyways, the Custom Extras folder is now a mirror of the XBMC home directory. So, in other words, anything you you put in there will show up the same way in your finished build.
Others will notice you can put modified source code into the Patches folder before you run XBMCDBR. The Patches folder is a mirror of the XBMC CVS repository. IT overwrites the CVS code with any of your customised sourc code before you compile(Helpful for those who like to use Patches that are not in the CVS or for developers/experimenters who like to play with the source code).
For instance, there is some people that like to edit the CVS file XBMC\xbmc\application.cpp to change the location of the webserver. You would Browse the XBMC CVS for the latest version of application.cpp, modify application.cpp to your liking, then put it into Patches\xbmc\application.cpp. This file will then overwrite the CVS version of the file in the CVS source directory before compiling. If you don't need it modified anymore, no problem, delete the custom file from the Patches folder and on your next CVS update the old file will be discarded and a new application.cpp from the CVS will take it's place.
Hope this clears this up.
I noticed that there is no XML folder in the Customs Extra folder. Is this by design, or an oversight? I created my own, added the XML file to it (xboxmediacenter.xml), but it wasn't uploaded to the Xbox. It uploaded an original, unmodified xboxmediacenter.xml file. Was I supposed to create the same XML folder under patches as well?
One problem I ran into is I got .NET error at the end of the process, and XBCDBR had to be ended manually. However, It still successfully completed the job, including FTP'ing to the Xbox. I'll try reinstalling .NET to see if this helps.
One suggestion I would have for the XBMC tool kit is a tool that easily allows you to make XBMC skins.
By the way, very nice job.