ASP.NET Webparts application + Publish site = loose page content

[ryan.mclean]

Hi all, I have a strange problem and I think it may be something in my
web.config . . . but I'm not sure.

I have an application that uses webpart (not sharepoint), but the nifty
new .net webparts . . . and it works great, we are using sql server for
the personalization provider. Parts can be added and used, not obvious
error. Close the page open it back up; everything is there. When we
debug or publish the project, all of my zones are empty and the site is
back to the default setup, just like if I pulled a:

WebParts.Person alizationAdmini stration.ResetA llState(WebPart s.Personalizati onScope.User)

Here is my personalization node from the web.config:

<personalizatio n defaultProvider ="AspNetSqlPers onalizationProv ider">
<!-- Providers may only be defined at the application level -->
<providers>
<clear/>
<remove name="AspNetSql Personalization Provider"/>
<add name="AspNetSql Personalization Provider"
type="System.We b.UI.WebControl s.WebParts.SqlP ersonalizationP rovider"
connectionStrin gName="SQLConne ctionString"
applicationName ="EBMSIntran et"/>
</providers>
<authorizatio n>
<deny users="*" verbs="enterSha redScope"/>
<allow users="*" verbs="modifySt ate"/>
</authorization>
</personalization >

And the relevant connection string:

<add name="SQLConnec tionString"
connectionStrin g="Server=SERVE R;Database=aspn etdb;UID=User;P wd=super-secret-password;"/>

I hope it is something easy i need to add or remove . . . thank you for
any help you can offer.

Have a great weekend,
Ryan

[ryan.mclean]

Oh my gosh, i knew it would be easy . . . here is my great solution.
Simply add:

Personalization-Enabled="true" Personalization-InitialScope="U ser"

to the webpartmanager. Sheesh, like I said, at least it was an easy
solution.

Thanks anyway,

Ryan

ry*********@gma il.com wrote:

Hi all, I have a strange problem and I think it may be something in my
web.config . . . but I'm not sure.

I have an application that uses webpart (not sharepoint), but the nifty
new .net webparts . . . and it works great, we are using sql server for
the personalization provider. Parts can be added and used, not obvious
error. Close the page open it back up; everything is there. When we
debug or publish the project, all of my zones are empty and the site is
back to the default setup, just like if I pulled a:

WebParts.Person alizationAdmini stration.ResetA llState(WebPart s.Personalizati onScope.User)

Here is my personalization node from the web.config:

<personalizatio n defaultProvider ="AspNetSqlPers onalizationProv ider">
<!-- Providers may only be defined at the application level -->
<providers>
<clear/>
<remove name="AspNetSql Personalization Provider"/>
<add name="AspNetSql Personalization Provider"
type="System.We b.UI.WebControl s.WebParts.SqlP ersonalizationP rovider"
connectionStrin gName="SQLConne ctionString"
applicationName ="EBMSIntran et"/>
</providers>
<authorizatio n>
<deny users="*" verbs="enterSha redScope"/>
<allow users="*" verbs="modifySt ate"/>
</authorization>
</personalization >

And the relevant connection string:

<add name="SQLConnec tionString"
connectionStrin g="Server=SERVE R;Database=aspn etdb;UID=User;P wd=super-secret-password;"/>

I hope it is something easy i need to add or remove . . . thank you for
any help you can offer.

Have a great weekend,
Ryan