I'm really struggling with some of the design concepts behind Sitefinity.
For example, a lot of configuration is held in XML in the App_Data folder, but the application seems to want to change these files itself. This is causing many issues with versioning, source control and working locally connected to a shared dev database. We've tried following the guide to 'store config in the database', however the app_data .config files still have to exist and are still updated! Why? if the idea is that it's stored in a database?
There also seems to be odd dependencies on specific versions of these files. When one developer updates their local installation, breaking changes are made to the shared development database, and the .config files. I find the whole idea of guids that have to stay in sync accross a database and local config files odd.
Finally, if the application throws any kind of error, it appears to shut itself down and restart, which takes around 60 seconds. This worries me - if one user causes some form of error, the whole application becomes unavailable?
I appreciate I may be missing something with these observations. Does anyone have more information or workarounds to offer?