Comments on: Including additional assemblies in the WSP with Visual Studio SharePoint development tools

By: chamika

chamika — Mon, 31 Oct 2011 08:03:14 +0000

nice post. Thank you very much. This saved my time. All the best.

By: Matthias Fonteyne

Matthias Fonteyne — Fri, 05 Aug 2011 12:36:33 +0000

Thanks!
This is just what I needed!

By: Waldek Mastykarz

Waldek Mastykarz — Wed, 06 Apr 2011 14:50:54 +0000

@BUJY: I've just tried it, following the description in this article, and everything seems to work correctly. Are you sure you have done everything correctly?

By: BUJY

BUJY — Wed, 30 Mar 2011 11:15:31 +0000

I want to use your described solution with Imtech.VisualStudio.SharePoint.Tasks…so far so good…the problem is that sharepoint 2010 is based on framework 3.5 and your assembly is built with framework 4..this result in conflicts during build and the custom task will not run and replace the token $Imtech.VisualStudio.SharePoint.Tasks$

By: Waldek Mastykarz

Waldek Mastykarz — Fri, 18 Mar 2011 13:16:34 +0000

@Shyam: Just because the project is in the same Visual Studio solution, it doesn't mean that it will be included in the WSP Package. In this article I showed how you could include another assembly, which not necessary have to come from a SharePoint project, in the WSP Package so that it will be deployed to the SharePoint Farm.

By: Shyam

Shyam — Thu, 17 Mar 2011 01:19:07 +0000

Good post. Thanks.

But, I just want to point out that, under the following circumstances, i don't think you need to create any custom task to do this.

1. All the projects are built under one build routine 2. Share the same version information and public key token.

If these two conditions are satisfied, then you should be able to use ", Version=$SharePoint.Project.AssemblyVersion$, Culture=neutral, PublicKeyToken=$SharePoint.Project.AssemblyPublicKeyToken$" anywhere you need to make the assembly reference to a strong named assembly. Correct me if i'm wrong.

By: Waldek Mastykarz

Waldek Mastykarz — Thu, 06 Jan 2011 11:32:07 +0000

@Andres: you need to add it as a reference to your project so that Visual Studio is able to use it for resolving types. The good news is that you can make the reference point to the same file to avoid duplication.

By: Andreas

Andreas — Wed, 05 Jan 2011 10:11:12 +0000

Hello,

I got a question regarding this topic. I've added a dll to my package and now I would like to use this dll in my SharePoint solution. Do I have to add it again (or maybe only?) via reference or is there a possibility to access the dll which will be included in the package?

By: Include additional assemblies in a wsp package in visual studio 2010 @ The Buzz Blog

Thu, 04 Nov 2010 14:15:43 +0000

[...] http://blog.mastykarz.nl/including-additional-assemblies-wsp-visual-studio-sharepoint-development-to... work2010, sharepoint, visual studio [...]

By: SP2010: Adding dll’s to WSP « RaSor’s Blog

SP2010: Adding dll’s to WSP « RaSor’s Blog — Sun, 17 Jan 2010 15:25:16 +0000

[...] http://blog.mastykarz.nl/including-additional-assemblies-wsp-visual-studio-sharepoint-development-to... Leave a Comment [...]