Joe, thanks for the great job on the profile feature! It's really great.


Still, there are some my thoughts on how to improve it.

1. Need to add default values for all the profile property options to documentation (and implement it if it is not done already). As a result I do not need to write, for example, 'lazyLoad="false"' for each profile property. It would be nice to place this documentation to the beginning of mojoProfile.config.

2. Some web interface to manage the properties list would be great, but not so nesessary.

3. Need property option like 'VisibleOnWeb="false"' to prevent the property from showing to anyone, even web site administrators. Such properties can be accessed only from the code and store some technical information attached to the user).

4. If I add my custom properties, all the strings are in the same resource file. So, when I translate both mojoPortal and my custom properties to russian, it would be difficult for me to share the translation. Optional custom profile property for resource file name or just text will be the solution.

5. If I add my custom properties or remove some standard ones I have a conflict with SVN file.
Possible solution is the following:
- move this section back to web.config
- add a property like <mojoProfile OptionalFileOfUserSpecificProperties="mojoProfileUser.Config">
- implement <add>, <clear /> and <remove> tags for this file
- ignore the option if this file does not exist
- add a template for this file to SVN (as you did for user.config).


6. Rules like "if the property name contains 'url' it is rendered as a link" do not seem to be a good style for me. May be, add type definitions something like that (it shall not work just as written below, but I just want to show the idea):

<mojoProfile>
    <types>
        <add name="text"
                type="System.String"
                editControl="System.Web.UI.WebControls.TextBox"
                editControlValueProperty="Text"
                viewControl="System.Web.UI.WebControls.Label"
                viewControlValueProperty="Text"
                viewControlAdditionalOptions=""
                ...
                >
        <add name="yesno"
                type="System.Boolean"
                editControl="System.Web.UI.WebControls.CheckBox"
                editControlValueProperty="Checked"
                viewControl="System.Web.UI.WebControls.CheckBox"
                viewControlValueProperty="Checked"
                viewControlAdditionalOptions="Enabled=false"
                ...
                >
        ...
    </types>
    <properties>
        <add  name="MSN"
                type="text"
                ...
                >
        ...
    </properties>
</mojoProfile>

Or just hardcode several types for text, number, positive_number, date, link, yesno, etc.

1. Ok. Please, add it also to the beginning of mojoProfile.Config.

2. Ok, I also think it's not so nesessary.

3. I mean some non-humanreadable user properties of my custom pages. Something like timestamps for remote operations, etc.

4. Ok.

5. You have already implemented an <add tag>, i just meant to implement the rest 2 as they are rather simple.
It's not good that "mojoProfile.Config" file name is hardcoded. As this file is stored in SVN, the easiest way to minimize conflicts is to create my own congig file and to change Web.config as
<mojoProfile configSource="myProfile.config"></mojoProfile>
May be, just remove the line above from Web.config and add a new property to appSettings section like "ProfileConfigurationFileName"? In this case it will also be easy to overwrite it in user.config without any conflicts in Web.config.

6. May be, you are right - your solution is much more easy... But it still requires some more types like date.

Still waiting for ResourceFile property and documentation on the default values.

1. About resourceFile property. I did not see it in the picture, so I did not notice the change of the documentation page. Thanks.

2. About documentation on the default values. Even if I know it is there I still cannot see it for all properties. Can you please add some more-user-friendly documentation, just say for each property if it is optional and default value like that:

name (mandatory) - must be unique for each property in the mojoProfile.config file, it is the name of the property.

lazyLoad (optional, defaults to "false") - in most cases you do not need it. When set to true, the property will be loaded from the database on demand rather than as a group with the other profile properties. This should only be true for seldom used or particularly expensive to retrieve properties.