As we are evaluating Sitefinity v4.0, we are also evaluating how developer friendly it is. One minor annoyance is how well v4 RC integrates with our source code control. Since a single project may be shared across multiple developers, we need to include configuration files that are stored in the App_Data folder in source control - this way one developer's changes in any of the modules for example, would be updated in another developer's instance when they perform a "get all" from source code control.
That being said, when the administrative interface needs to make an update to one of the config files that are checked in, it will error, saying that a config file could not be written to. This is fine as the developer simply needs to check out the file, try saving again, and then check in once completed.
When the administrative interface adds a config file, VS isn't aware of the new file. The developer would have to constantly check to see if there are any new files added, then add them manually to VS. Minor annoyance, but I can see how something could accidentally be left out.
Finally, when the SecurityConfig.config is checked in (therefore marked as read-only), the entire SItefinity application fails, saying "Access to the path - - -\App_Data\Sitefinity\Configuration\SecurityConfig.config' is denied.
" When marking the file as writable, the site then works. So I'm not sure why Sitefinity won't work properly if this file is marked as read-only?
Any word on getting v4 fully compatible with WIndows Azure? From what I understand in other posts, the problem lies with the App_Data folder not being writable in Azure. Will Telerik be addressing this issue?
Again, these are just very minor annoyances. I feel that v4 is an awesome awesome product and very much look forward to upgrading our current site and promoting v4 to all of our clients. I congratulate Telerik, especially the Sitefinity team on a great product.