Error in Extensibility Kit

Question

I am trying to compile the existing Extensibility  web part project " SharePointCommerce.sln " as follows,http://localhost:38161/ http://localhost:38161/

 

1. Created a new Key using sn tool

2. Referred the newly created key in all project file within that solution.

3. Build the solution file.

4. Uninstall all Microsoft.Commerce.Portal.* DLL from GAC

5.Copy & Paste the new DLL into GAC

4. Then updated the public key reference of Microsoft.Commerce.Portal.*  in all required file with the new one, using find & replace.

5. Again build the solution.

6. Now I retract & remove the existing default site & web part solution from SharePoint.

7. Then I deployed the newly created solutions into SharePoint.

8. When I tried to create new web site & site collection, it created successfully, but when I tried to access the site, it throws  error, stating Microsoft.Commerce.Portal.SharePointCommon (with old public key) is missing.

 
Actually it refer to the old DLL.

 

 

 

Any thought would be appreciated.
Thanks!

Answer 1

Hi
Check the dll in the IIS where your sharepoint site hosted, wether it has new snk or old..

Also recheck the webconfig of the site where we out the reference of dll , wether it contains old public key or new

---

Vijay Sagar

Answer 2

Thanks!
It has the new DLL in both place.

Answer 3

HI,
Look, if there are some XML files in the 12 hieves and there are reference of dll is manitaned , can please check into those xml files

basically these xml files for custom controls , if extensibility solution have created some code for custom control then there should be a refernce of dll in there repective xml files and these files should be keep in C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\XML...

---

Vijay Sagar

Answer 4

Have you tried
- Deactivating and reactivating the Commerce Server Features at the site and site collection and web application levels?

- Restarting the Windows SharePoint Services Timer  service?

Answer 5

Have you tried IISRESET?

Answer 6

Hi,

I would strong advise using SharePoint solution deployment through STSADM instead of simply switching out the assembiles. If you download WSPBuilder from CodePlex (http://www.codeplex.com/wspbuilder) and compile your solution, and use the tool to build a WSP file you can deploy into SharePoint farms alot simplier and has a better supported upgrade and retraction path. 
 
So possibly uninstall the default Commerce Server features (or deactivate them from your application) build your new solution into a WSP, and deploy from there. You should have no assembly caching issues using this approach.

Thanks,
Lewis

---

Follow Me on Twitter: @LewisBenge Or check out my blog: http://www.geekswithblogs.com/pointtoshare/

Answer 7

Hi,
If you are using the MOSSCSContemporarySite, the steps are as follows:
1. Create new key
2. Build all the web parts
3. With SPD, change all applicable dll references in application and test. Also in web.config.
4. If it all works for you, make changes to C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\TEMPLATE\SiteTemplates\MOSSCSContemporarySite. Also in C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\TEMPLATE\SiteTemplates\MOSSCSDefaultSite. There should be a couple of 100 or so. 4. Test with SPD.
5. Open VS and create new site definition project. Easier if you just use WSP Builder (Codeplex). Add files from 12 hive to project.
6. A couple of iterations and you've finished.

Good luck.
Step

Answer 8

Thanks! For all your support. After Deactivating & Activating the site features, it works fine.