What is the syntax for changing the provider for Personalization? I tried to do the same thing as I do with the <membership> section but the syntax must be different. I get this error:

Provider must implement the interface 'System.Configuration.Settings.ISettingsProvider'.

I would like both Membership and Personalization to use a SQL Server provider.

Thanks,

Scott, have you tried the following in your web.config:

<personalization enabled="true" defaultProvider="AspNetSqlProvider" />


<pagePersonalization enabled="true" defaultProvider="AspNetSqlProvider" />

---

Shanku Niyogi





This posting is provided "AS IS" with no warranties, and confers no rights.

Yes, I believe that part I have right. It's defining the provider itself that I'm missing. Here is what I have:

<anonymousIdentification enabled="true"/>
<personalization enabled="true" defaultProvider="WhidbeyPersonalization">
<profile>
<property name="PostalCode" allowAnonymous="true" />
</profile>
<providers>
<add name="WhidbeyPersonalization" type="System.Web.Security.SqlMembershipProvider, System.Web, Version=1.1.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
connectionStringName="AspNetSqlProvider"
applicationName="/membership" />
</providers>
</personalization>

Basically I tried to copy the Syntax from the Membership section that is working correctly. I have the AspNetSqlProvider connection string defined in machine.config and that works correctly for Membership.

Thanks again,

The SqlMembershipProvider class does not do personalization - it's only a membership provider. That's why you're getting the type mismatch.

You don't need to add the provider definition in web.config. If it has been defined in machine.config, that definition is automatically inherited into the app level config. All you need to do is set the defaultProvider to point to it by name. If you do want to add your own new provider definition, use a copy of the format used in the <personalization> section, not the <membership> section, of machine.config.

---

Shanku Niyogi





This posting is provided "AS IS" with no warranties, and confers no rights.

Doh! Note to self: Use machine.config for syntax examples.

I did need to create a custom profile since I'm using a remote SQL Server, but as you suggested everything I needed was in machine.config. Ultimately I wanted to set machine.config but I was working from the wrong direction and trying to get it working in web.config first, forgetting the examples that machine.config has.

It works great now.

Thanks,

In documentation, there's a claim that any data provider can be used.

I'm hoping to use postgresql for some home projects since the costs for sql server are wayyy too much for me (Just renting the server is gonna cripple me).

Any pointers in how to get profiles to work thru postgresql?

---

Rar!

You can create a custom profile provider by creating a class that inherits the ProfileProvider abstract class. Depending on how you connect to postgresql (OLE DB, ODBC, other), you simply add your own specific data logic. There's an example profile provider in the documentation. The MSDN version of the documentation is currently found at http://msdn2.microsoft.com/en-us/library/0580x1f5.aspx. The sample included in the documentation uses the classes in the System.Data.Odbc namespace.

HTH

Doug Rothaus


This posting is provided "AS IS" with no warranties, and confers no rights.