Tell me more ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.
up vote 1 down vote favorite

My Sharepoint project has a webpart, which references dlls without strong names, which in turn further reference other dlls without strong names.

Is it possible to add these dlls to sharepoint without the strong naming?

Amongst others, I am using Microsoft.Practices.EnterpriseLibrary.Common as well as other custom dlls.

Possible?

thanks,

KS

share|improve this question

2 Answers

up vote 1 down vote accepted

The source code is readily available for the Enterprise Library so if you are going to use it, you should rebuild it using one of your keys so that it can be put in the GAC and then easily reused by other applications. Once that is signed, you should do the same with your web parts.

However, if you wish to DLLs without strong names then you will need to place all of them in the /bin/ or /_app_bin/ folders of the web application in question. You may also see security restrictions as a result of this. Also, if you have multiple web applications then you will need to copy them to place them in the proper folders for all web apps that will need them. You can see how this could easily become a significant maintenance and troubleshooting issue.

share|improve this answer
Problem is that my sharepoint project wont compile unless the references which I add (the dlls in question) are strong-named. So I can put in the BIN no problem, but I cannot deploy the webpart because of the compilation error. – Perplexed Mar 20 '12 at 15:39
@Dave am not clear with you point. Could you please confirm, whether we can use with out strong name or we should have use with strong name. If you are saying strong name not required and we can use from web application bin folder, please provide me steps to achieve this. I have tried to access unsigned(without strong name) from bin/_app_bin folder, Webpart Project bin folder but all of these requires strong name. Waiting for your update, Manikandan – user7773 Apr 9 '12 at 12:20
up vote 0 down vote

It is recommended to ensure you are referencing the correct assembly (give it a unique identity), and give it added security with a digital signature.

You can reference third party assemblies if you want to, using the Visual Studio command prompt tools:

http://sharepointcoding.wordpress.com/2009/02/27/assign-a-strong-name-to-a-third-party-dll/

Here is an article on assigning strong names specifically to the Enterprise Library assemblies: http://www.codeproject.com/Articles/21389/Using-Microsoft-Enterprise-Library-Application-Blo

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.