Calling all developers! We invite you to provide your input on Feature Experimentation by completing this brief survey.
Calling all developers! We invite you to provide your input on Feature Experimentation by completing this brief survey.
I think it could work fine if you set the automaticSaveEnabled to false. Or you can intercept this in the Global.asax:
void Profile_ProfileAutoSaving(object sender, ProfileAutoSaveEventArgs e)
{ e.ContinueWithProfileAutoSave=false;}
In ProfileModule ( EPiServer.Business.Commerce ), you could also see that it intercepts this event if the HttpContext.Items["CancelProfileAutoSave"] is true.
if ((e.Context.Items["CancelProfileAutoSave"] != null) && ((bool) e.Context.Items["CancelProfileAutoSave"]))
{
e.ContinueWithProfileAutoSave = false;
}
In the enotaca sample site, the site uses the SqlServerProfileProvider, but it is configured with automaticSaveEnabled=true, which means that every single page view will result in a call to a stored procedure which will perform a number of selects and potientially an update to the database. This is bad for performance, so i was wondering if this setting is needed for Commerce to function properly or if i can disable it?