Hello,

 There are a couple of ways to create custom profile data types.

1.) To create a custom profile data type to store multiple string values, you first need to create a class that inherits from ProfileBase that defines your profile properties in the App_Code folder. The class should look like this:

using System;
using System.Collections;
using System.Collections.Generic;
using System.Web.Profile;

public class CustomProfileClass : ProfileBase
{
    public CustomProfileClass() {}

    public List<String> Models
    {
        get { return (List<String>)base["Models"]; }
        set { base["Models"] = value; }
    }
}

2.) To create any other custom profile data types that would like to your web.config. Notice the inherite attributes points to your custom profile class.

<profile enabled="true" defaultProvider="AspNetSqlProfileProvider" inherits="CustomProfileClass">
      <providers>
        <clear />
        <add name="AspNetSqlProfileProvider" type="System.Web.Profile.SqlProfileProvider" connectionStringName="ASPNETMembershipDB" applicationName="/" />
      </providers>
      <properties>


        <add name="DisplayName" type="string" allowAnonymous="true" />
        <add name="ContactEmail" type="string" allowAnonymous="true" />

      </properties>
    </profile> 

You should now notice that the Profile object shows your custom data types in Intellisense. You can add values to the custom data types similar to:

Profile.DisplayName = this.txtDisplayName.Text;

Profile.ContactEmail = this.txtContactEmail.Text;

foreach (ListItem item in lbxModels.Items)
{
          if (item.Selected == true)
              Profile.Models.Add(item.Value);
}

Thanks,

Andrew

Andrew,

Thanks for the reply.  It looks like your example uses the standard AspNetSqlProfileProvider, though, and I am using the SqlTableProfileProvider (available here: http://www.asp.net/sandbox).  I'll take a look, though, and see if the same code will work.

 -Joel
 

The above code will not work with the SqlTableProfileProvider.  I can't even get the default provider to store Guids.

Somebody in the Sandbox crew neebs to produce a real White paper on the SqlTableProfileProvider rather than the one they have.  At least tell us what we can and cannot do with it, and what code that works in the default provider will not work in this.  Right now everything is a *** in the dark, almost renders it useless in my opinion.