You searched for the word(s): userid:465816

More Search Options

RSS Available

• Re: Personalizable Dictionary

  If you are manipulating an object and the object reference is not changed after the data is loaded, personalization framework cannot distinguish whether the object is dirty or not. To force personalization data to be saved, you can call the static function WebPart.SetPersonalizationDirty(Control) for your custom control or SetPersonalizationDirty() on your custom webpart. Hope that helps, Helen

  Posted to Web Parts and Personalization (Forum) by helenyan on 12/14/2005

• Re: How can I personalize a WebControl?

  Thanks for the repro code that you provided offline. The Controls.Count problem that you mentioned with WebControl is because in general, WebControl class is not recommended for cases where you have child controls. For this case, the CompositeControl is a better substitute. CompositeControl ensures that child control collection is populated when Controls property is accessed. This is essentially what WebPart does internally. If CompositeControl or WebPart are not adequate for your needs, you'll need

  Posted to Web Parts and Personalization (Forum) by helenyan on 11/30/2005

• Re: Update Framework - possible with VS Beta 2 ?

  There was a change in the membership/profile/personalization schemas moving from beta2 to RTM, which is why you get the error. You can upgrade the schemas as follows: (also on http://forums.asp.net/1085942/ShowPost.aspx ) (1) If you are using a SQL database: run aspnet_regsql.exe from the .NET framework install folder. Specify the connection string and the same database name. This will upgrade the schemas without changing the table contents. You can run without any command line arguments and go through

  Posted to Installation and Setup (Forum) by helenyan on 11/29/2005

• Re: Enums

  Answered in http://forums.asp.net/1095687/ShowPost.aspx . Helen

  Posted to Web Parts and Personalization (Forum) by helenyan on 11/14/2005

• Re: Enums

  I understood your problem and I'm able to repro the exception now. Since the type is in user control, rebuilding the website is causing the persisted enum type reference to be invalid. This is why you're getting the argument exception. Unfortunately, we currently do not have special detection in user controls to keep track of these type changes. The workarounds would be to extract the enum type into a separate class file and place into App_Code, or precompile it into assembly. To get the page to

  Posted to Web Parts and Personalization (Forum) by helenyan on 10/25/2005

• Re: Personalize the treeview control...

  One way you can personalize a treeview control is by overriding the treeview control, expose the properties that you want to be personalizable by users and put that control in the webpartzone. An example is a simple custom treeview which allows users to personalize the foreground color: public class PersonalizableTreeView : TreeView { [ Personalizable ] <-- override this property and mark it personalizable public override System.Drawing. Color ForeColor { get { return base .ForeColor; } set {

  Posted to Web Parts and Personalization (Forum) by helenyan on 10/24/2005

• Re: Trouble moving web parts from one zone to another.

  Is it possible that the current user is not authenticated? Are you using Forms or Windows auth? Can you check the values of Page.User.Identity.IsAuthenticated and Page.User.Identity.Name? When the current user is not authenticated, the Personalization scope will be defaulted to "Shared" and the current user does not have the permission to modify personalization state. Hope that helps. Helen

  Posted to Web Parts and Personalization (Forum) by helenyan on 10/24/2005

• Re: problem in browing webpart aspx page(asp.net 2.0) from IIS 6.0

  If you have migrated from whidbey beta2 to this version, you will get this error. You can upgrade the schemas as follows: (1) If you are using a SQL database: run aspnet_regsql.exe from the .NET framework install folder. Specify the connection string and the same database name. This will upgrade the schemas without changing the table contents. You can run without any command line arguments and go through the GUI. Alternatively, you can run with command line arguments similar to " aspnet_regsql -A

  Posted to Web Parts and Personalization (Forum) by helenyan on 10/18/2005

• Re: Oracle & Web Parts

  Sorry about the confusion... "ProviderCode" should be substituted with the namespace you declared for your provider class. "CustomPersonalizationProvider" should be substituted with the class name you declared for your custom PersonalizationProvider. To use an oracle provider, you'd have to implement a custom OraclePersonalizationProvider that inherits from PersonalizationProvider class. Add this in the web.config as an available provider (shown in post above) and then specify it to be used as a

  Posted to Web Parts and Personalization (Forum) by helenyan on 9/20/2005

• Re: PersonalizationScope.Shared problem

  Specifying [Personalizable(PersonalizationScope.User)] indicates that the property can be personalized when page is in Shared or User scope. On the other hand, specifying [Personalizable(PersonalizationScope.Shared)] indicates that the property can be personalized only when page is in Shared scope. Property values saved in Shared scope are applied as "default" values if the properties have not already been customized by individual users. If you desire to save shared personalization data, the page

  Posted to Web Parts and Personalization (Forum) by helenyan on 9/12/2005