Assembly *.dll must be strong signed in order to be marked as a prerequisite

Hello all ,
I am refrencing dll in my project and it gives this error
"Assembly *.dll must be strong signed in order to be marked as a prerequisite"
while it worked before now it doesn't work.
any suggestions ?
LVL 4
AhmedHindyAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

melmersSenior Software Deveolper/ArchitectCommented:
You can try 2 things which helped me sometimes.

1.) Delete the bin and obj directories of oyur projects and then rebuild all.(Ensure that your build configuration manager has all project marked to build)

2.) Add and Remove the references you need for your projects. If you updated the files with newer
     version with filecopy it can ends in this type of error.

Do you sign & strongname you project?
If you use ClickOnce deployment try to deactivate the security settings.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Walter PadrónCommented:
This happens when two projects references different version of the same assembly and the solution could be to upgrade the packages.

Also follow @melmers suggestion of delete the bin and obj folders and then Rebuild All

Best regards
topdog770Commented:
Another option is that the signed assembly is located in the GAC and there's a local copy that's interfering with the signged version.

1) Start by removing any local copies of the DLL, if the app builds and runs ok then you've just proven this to be the problem.

if problem persists, then a more thorough clean up is required.
Naman GoelPrinciple Software engineerCommented:
My guess is that you're not working with strongly named assemblies. I've had this error when two projects reference slightly different versions of the same assembly and a more dependent project references these projects. The resolution in my case was to remove the key and version information from the assembly name in the .csproj files (it didn't matter anyway), and then do a clean build.
Martin LissOlder than dirtCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
C#

From novice to tech pro — start learning today.