Adding Extended Web Parts

  • Article

If you have an existing site where you have installed and deployed the SharePoint Commerce Services Web Parts and want to deploy the extended Web Parts to this site, you must use your own signing key because Commerce Server 2009 R2 installs SharePoint Commerce Services with a Microsoft delay-signed key. The delay-signed key will prevent you from deploying the extended Web Parts to production.** **

Key Replacement

You will have to generate your own strong named key pair and attach it to the projects.

All instances of the public token from the Microsoft delay-signed key have to be replaced with the newly-created public token. The public token is found throughout the source code, in both the ASCX and XML files.

To Replace Installed Web Parts with Extended Web Parts

To replace previously installed Web Parts with extended Web Parts, the pages of the site must be updated with the new public token by using SharePoint Designer.

Note

Deploying any extended Web Parts over the previously deployed Web Parts from SharePoint Commerce Services without updating the token will break the existing site.

Note

For a SharePoint Server 2010 installation, you only need to modify the pages on the variation root and it will propagate the changes (after you publish your changes) to the site variations. For a SharePoint Foundation 2010 installation, you have to modify each instance of that page for each locale.

Note

You must be a Site Collection Administrator to perform the conversion.

To convert to a new signing key for an existing Commerce Server site

  1. In SharePoint Designer, check out all Master pages, page layouts, and pages that have the public key token.

  2. For each page, right click the page, and then select Detach from the page layout. This is not required for the Master Page.

  3. Find and replace the old key with the new key by using Search in source code from the Find and Replace Tool.

  4. Save all changes.

  5. Reattach all pages to their page layouts.

  6. Deactivate all Commerce Server 2009 R2 features using the SharePoint Server Stsadm command-line tool.

  7. Retract and remove the Commerce Server 2009 R2 WSP file (this is the one with the old key).

  8. Redeploy the new WSP file (the one with the new key) and activate features.

  9. Update the public key tokens in the XSL transforms saved on the site in the Commerce Server 2009 R2 templates library, for example, templates that the Product Query Web Part uses. This applies to all Web Parts that use XSL transforms actions where the Web Part needs the class type in the XSL transforms to instantiate the control.

  10. Test the site.

  11. Check in your changes with SharePoint Designer.

  12. Publish and approve the pages if required by the site collection.