Web Parts: Best Practice, Optimization and Health Monitoring

Last post 01-16-2008 8:35 AM by littlefool. 3 replies.

Sort Posts:

  • Web Parts: Best Practice, Optimization and Health Monitoring

    01-11-2008, 3:58 AM
    • Loading...
    • kcube
    • Joined on 07-07-2006, 4:11 AM
    • Kochi
    • Posts 77
    Hi,We are on the move to implement Web parts, can anyone help me to get the resource related with Web parts integration, best practice, optimization and health monitoring.Is there any problem in storing the personalization data in “App_Code”, if the numbers of users are more? What all are other options to store personalization data of Web Parts. Thanks in advance.KCube

     

    Regards,
    KCube

    [Mark As Answer! If this helps you]
  • Re: Web Parts: Best Practice, Optimization and Health Monitoring

    01-13-2008, 8:34 PM
    • Loading...
    • vinz
    • Joined on 10-05-2007, 11:47 AM
    • Cebu Philippines
    • Posts 8,260

    With regards to personaliztion then you can refer to this link

    http://msdn2.microsoft.com/en-us/library/z36h8be9.aspx

     


    Regards,
    Vincent Maverick Durano

    Please post questions to the forums, where others may benefit.I do not offer free assistance by e-mail. Thank you!



  • Re: Web Parts: Best Practice, Optimization and Health Monitoring

    01-16-2008, 5:21 AM
    Answer

    Hi,

    The more about the webpart and the some samples, you can check this link: http://quickstarts.asp.net/QuickStartv20/aspnet/doc/webparts/default.aspx 

     Hope it helps.

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.


    Yours sincerely,
    Amanda Wang
    Microsoft Online Community Support
  • Re: Web Parts: Best Practice, Optimization and Health Monitoring

    01-16-2008, 8:35 AM
    Answer
    • Loading...
    • littlefool
    • Joined on 03-05-2004, 1:28 AM
    • Oslo, Norway
    • Posts 129

    Hi, WebPart Personalization makes also use of the ASP.NET 2.0 Provider Model. This means that a provider is in charge of writing the data to a data source. You can always override the provider to make the data storage custom to your personal needs. More info of the providers model can be found here http://msdn2.microsoft.com/en-us/library/aa478948.aspx.

    Personalization uses the Web Parts Personalization provider http://msdn2.microsoft.com/en-us/library/aa478955.aspx.

    Because you overwrite the provider, you are in full control what and where you save the data. This article has an example of saving the personalization data in a text file in the App_Code folder of your site. http://msdn2.microsoft.com/en-us/library/aa479037.aspx

    Hope this will give you some starting points. I myself am also just starting to read and experiment with Web Parts because we would like to start using it in a dynamic portal.
    I can also recommend the book ASP.NET 2.0 Web Parts in Action (Darren Neimke, Manning) http://www.manning.com/neimke/

    "Dream as if you'll live forever, live as if you'll die today" (James Dean)
Page 1 of 1 (4 items)
Microsoft Communities
Page view counter