XBMC4Xbox

This is an inquiry into how the plugin performs.
Is XBMC4Xbox Installer intended as (in a sense) a 'nightly build patcher', and for stable build updates it is still recommended to FTP? Or is it recommended by forum members to update XBMC4Xbox stable build Updates using XBMC4Xbox Installer? As an example with the next stable build release would it be fine to update using XBMC4Xbox installer? Does this plugin overwrite already installed XBMC4Xbox files automatically when updating?

On a side note this is my first post and i would like to thank everyone here for all of your wonderful work.

@amvalk
I, as the author of XBMC4Xbox Installer program plugin (or as it used to be known as, XBMC SVN Installer) can recommend it, maybe a few other users too - the plugin is not quite official (as in not having the seal of approval from XBMC4Xbox Devs), it's just a personal contribution out of need, and in fairness inheriting some of the features from previous scripts / plugins doing similar jobs (credits in the link below).

I can also recommend reading its thread and more importantly the wiki page it refers to, that should maybe answers some of your questions.
http://www.xbmc4xbox.org.uk/forum/viewt ... p?f=7&t=88

The plugin does pretty much what you would do - download the package (build) off the internet, extract it in a new folder and asks you whether to "upgrade" (copy the UserData, plugins, scripts etc. from "old" (running) install to "new" install) or a "clean" install (with just what comes in the downloaded archive, no sources, default configuration etc).

The plugin doesn't overwrite anything, it extracts into a new folder with the same name as download package (e.g. XBMC4XBOX-32643) in the configured path (e.g. E:\Apps). It does offer a feature to set currently running XBMC4Xbox as a default dashboard, but it requires you to first install the Team XBMC shortcut tool for that feature to work correctly (what it does in that case it identifies where currently running XBMC4Xbox is installed and it updates the shorcut .cfg file with the location, again, same as you would do).

Technically there is no difference between a "nightly" (dev) and a "stable" zip package - they all have the same structure and they can run on their own. Why "nightlies" might not be recommended to normal users is that they contain gradual changes made every few days that could fix or break things, and then you would need to get the next "nightly" build that fixes that particular problem, which could maybe break something else instead and so on. The plugin can be used to migrate from any to any (stable / nightly in any combination), since the internal structure of the packages is the same, it doesn't know or care.