Re: About the new profile feature
1. all properties have defaults so it is not needed to put lazyLoad="false" I will update the documentation to indicate the defaults
2. might be nice but not a priority for me, things like this should be a server configuration so a config file is appropriate in my thinking, it is not something to change frequently. It would be much more complex to implement this on a per site basis.
3. yes I've been thinking about that but not sure its really needed. the mojoProfile.config file is for what does show up in the UI. It is already possible in code to create and retrieve arbitrary properties using SiteUser.GetProperty and SiteUser.SetProperty. As long as these have lazyLoad = true they won't add any weight to normal operations and as long as they are not configured in the config file they will not show up in the UI
4. Good point, I will add a ResourceFile property, which will default to ProfileResource, so custom properties can have a separate resource file
5. I agree its a problem. For some things developers may need to back up things, I'm just not sure how much effort its worth, there are other things in web.config that are also an issue for svn like if you want to use a different machine key. There are many things I would like to do in mojoPortal so I must choose my battles wisely.
You can already specify an alternate file from web.config
I'm not sure of what is involved to implement add, clear remove etc
One thing is though that in Medium trust you cannot access config sections at all so I catch a security exception when trying to get the config section and if the exception occurs I access the file directly as xml instead and in that case its hard coded to use mojoProfile.config
6. In trying to keep things simple sometimes a simple solution is acceptable even if it isn't pretty. I do think I want to make the display of boolean values use an image true.png or false.png and maybe this can come from the skin folder