I have taken the Multi-Page personalization provider sample I found on the web, and changed the get/set property for the GroupName to return a value from the webpage to determine which WebParts settings to use. This works perfectly in Visual Studio. In the aspnet_Paths table, it creates records for each item in the dropdown where the webparts have been personalized(Only personalization is in the shared scope).
When I deploy to the webserver where this application is to reside, the personalization doesn't work. The only record that it will pull from the aspnet_Paths table is the record for default.aspx, not the records based on the dropdown. Even when using the same database in VS that the website in IIS is using, I get different behavior.
The website is a virtual directory under a website, I'm not sure if this is the problem or what. Any thoughts on why the GroupName seems to be ignored when the website is deployed to IIS ?
Thanks.