VS 2013 Clients with SharePoint 2013 installed and a TFS 2012 (without SharePoint)?

Jun 30, 2014 at 3:30 PM
Hi!

Currently, we have this setup running well:
  • Dev machines: VS 2012 with SharePoint 2010 installed
  • A TFS 2012, compiling the VS 2012 solutions (without SharePoint being installed)
Now we want to add dev machines with VS 2013 and SharePoint 2013. They shall use the TFS 2012. Is this combination also supported? I mean, will the scripts work if I collect the files from the VS 2013 clients and will the TFS 2012 still compile VS 2012/SP 2010 solutions afterwards (besides VS 2013/SP 2013)?

Thanks in advance for any helpful answers!

Kind regards,
Daniel
Coordinator
Jun 30, 2014 at 5:38 PM
Hi,

To build SharePoint farm/sandboxed solutions (including SP2010 and SP2013), please use the scripts and follow the instruction at http://sharepointci.codeplex.com.

Thanks,
Xiaoying
Jul 1, 2014 at 9:14 AM
Hi Xiaoying,

thanks for your reply. I already have working build scripts for SP2010 and this is also not about CI deployment. My question is about build dependencies. Your project seems to handle them. The project you are referring me to seems to be about build and deployment scripts only. This is why I think that here is the right place to ask. Please tell me if I did not understand well. Thank you!

Kind regards,
Daniel
Jul 1, 2014 at 9:22 AM
Or to reword just parts of the problem:
  1. Can your scripts collect the build dependencies from a VS 20__13__/SharePoint 20__13__ machine and copy them to the right locations on a TFS 20__12__? The goal would be that the TFS 20__12__ can then build (not deploy) the VS 20__13__/SharePoint 20__13__ solutions.
  2. Afterwards, can the TFS 2012 still build (not deploy) the VS 20__12__/SharePoint 20__10__ solutions, as it does now?
Kind regards,
Daniel
Coordinator
Jul 1, 2014 at 6:45 PM
Ah, I see. Thanks for the clarification, Daniel. The script TfsBuildServerPrerequisites.ps1 mentioned in the documentation page does collect the build dependencies for you, but it's only limited to the files listed at http://msdn.microsoft.com/en-us/library/ff622991.aspx. If your project references more assemblies, you will need to either update the script or manually copy them to the build server.

Thanks,
Xiaoying