New answers tagged solution-package
The article you used, specifies that you have to add the dlls into the package -> advanced tab. I assume you have done this and then published & installed the WSP or deployed the project via VS. Note that SharePoint 2010 is based on .NET version 3.5 and GAC is c:\windows\assembly However, SharePoint 2013 is based on .NET framework 4.5. The directory ...
What I normally do when I want to add a webpart to a page using a feature (or Powershell for that matter) is the following: Add the webpart to a page in your development environment. Customize it using the web interface. Add content to the content editor webpart. Export the webpart as a .webpart or .dwp file. Include the .webpart/.dwp file in your ...
I would create a different WSP with those dependent assemblies. You can version and deploy this WSP independently. Just be sure to not GAC deploy these assemblies from your solution WSP.
Putting list definitions, instances, content types etc in the WSP package prevents one from maintenance headaches. Imagine someone creating lots of things by hand and forgetting to maintain a proper document. Moreover, it may result in gaining significant time to deploy compared to doing things by hand every time. Second, it is not always true that ...
Top 50 recent answers are included