locked
Webparts personalization RRS feed

  • Question

  • User791773689 posted

    Hello everybody,

    I begin with Webparts, as SQL Server 2005 databases cannot be opened on Windows 10 I have to implement a new PersonalizationProvider.

    In web.config I declare it like that :

    <webParts>
    	<personalization defaultProvider="perso">
    		<providers>
    			<clear />
    			<add name="perso" 
    				applicationName="WebApplication2"
    				type="WebApplication2.Sql2014PersonalizationProvider"
    				connectionStringName="AuthConnectionString" />
    		</providers>
    	</personalization>
    </webParts>
    

    The WebpartManager could not be displayed without this registration. Once this is in the web.config the page with the WebpartManager is displayed.

    Now, if I add a CatalogZone, with a PageCatalogPart in it, I am said that my PersonalizationProvider is not registered.

    Well, a second registration ?

    Or is my registration not so correct as that ?

    Sql2014PersonalizationProvider begins with "namespace WebApplication2".

    Sunday, September 30, 2018 4:46 PM

Answers

  • User791773689 posted

    Well, it seems I found the answer.

    In the ProviderName property of the Personalization child of the WebPartManager,

    webParts configuration, use key rather than name

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Sunday, September 30, 2018 9:26 PM