Another episode of my series about automated build of SharePoint full trust solutions with tfs 2013 and visual studio 2013.
If you followed my posts you must have noticed you dll’s were built but you didn’t have any wsp.
This is because by default msbuild doesn’t package your solutions. That’s pity isn’t it?
Here is some documentation telling us to add IsPackaging=true to the build definition as a parameter.
That gives us /p:VisualStudioVersion=12.0;IsPackaging=true
See you soon for other posts.
Quick update on my serie about automated build for sharepoint full trust solutions.
If you take a look at the second error I’m describing here you will notice that you have to replace two lines in order to make it work.
With update 4 it looks like Microsoft is preparing full 64 bits support for visual studio. New fix lines are now
<Import Condition="'$(Language)' == 'C#'" Project="$(MSBuildExtensionsPath32)\Microsoft\Windows Workflow Foundation\v3.5\Workflow.Targets" />
<Import Condition="'$(Language)' == 'VB'" Project="$(MSBuildExtensionsPath32)\Microsoft\Windows Workflow Foundation\v3.5\Workflow.VisualBasic.targets" />
Notice the appearing of 32 in the parameter name (the previous parameter doesn’t seem available anymore).
Have a nice time building solutions!