V
vbMark
Hello,
(ASP.NET 2.0 w/ C#)
I am trying to get my web app to use the production SQL server for all
user/profile information but it keeps creating the ASPNETDB.MDF file
(locally) when I use a custom profile property.
For example, I have this in the web.config:
<profile >
<properties>
<add name="MyCustom" allowAnonymous="false" type="System.String"
defaultValue="" />
</properties>
</profile>
It seems that when my program does something like:
Profile["MyCustom"] = "blah";
that the ASPNETDB.MDF is created.
I have the following in my web.config also:
<roleManager enabled="true" defaultProvider="CustomizedRoleProvider">
<providers>
<add name="CustomizedRoleProvider"
type="System.Web.Security.SqlRoleProvider"
connectionStringName="MyDB" />
</providers>
</roleManager>
<membership defaultProvider="AspNetActiveDirectoryMembershipProvider">
<providers>
<add name="AspNetActiveDirectoryMembershipProvider"
type="System.Web.Security.SqlMembershipProvider"
connectionStringName="MyDB" />
</providers>
</membership>
So testing locally everything is using the SQL Server database for all
user information except using a custom Profile property.
What is going on and how do I stop this behavior?
Thanks!
vbMark
(ASP.NET 2.0 w/ C#)
I am trying to get my web app to use the production SQL server for all
user/profile information but it keeps creating the ASPNETDB.MDF file
(locally) when I use a custom profile property.
For example, I have this in the web.config:
<profile >
<properties>
<add name="MyCustom" allowAnonymous="false" type="System.String"
defaultValue="" />
</properties>
</profile>
It seems that when my program does something like:
Profile["MyCustom"] = "blah";
that the ASPNETDB.MDF is created.
I have the following in my web.config also:
<roleManager enabled="true" defaultProvider="CustomizedRoleProvider">
<providers>
<add name="CustomizedRoleProvider"
type="System.Web.Security.SqlRoleProvider"
connectionStringName="MyDB" />
</providers>
</roleManager>
<membership defaultProvider="AspNetActiveDirectoryMembershipProvider">
<providers>
<add name="AspNetActiveDirectoryMembershipProvider"
type="System.Web.Security.SqlMembershipProvider"
connectionStringName="MyDB" />
</providers>
</membership>
So testing locally everything is using the SQL Server database for all
user information except using a custom Profile property.
What is going on and how do I stop this behavior?
Thanks!
vbMark