Mostly figured it out. Hopefully I don't need to repeat it because it looks like an involved process:
I've got it building on my dev box in a separate workspace and publishing to a drop area. Something not unlike this article: http://msdn.microsoft.com/en-us/library/ff624126.aspx (How to Build Visual Studio 2010 Office Development Projects with TFS Team Build 2010), except for VS2012, Jenkins, and Office 2013 PIAs. On Dec 27, 1:28 pm, mwpowellhtx <[email protected]> wrote: > I should say: the latest PIAs: Office 2013 at the time of this post. > > On Dec 27, 1:27 pm, mwpowellhtx <[email protected]> wrote: > > > > > > > > > Hello, > > > I've got an Visual Studio Tools for Office Excel AddIn that I am > > scheduling for build. I build the Debug and Release versions, and that > > seems to be going well. I'd like to add a step that publishes to a > > staging folder, possibly share for folks to demo, evaluate release > > candidates, etc. Possibly ClickOnce style, if possible: trick being > > it's built against Office PIAs. I searched the group and to my > > surprise didn't find anything "publish". Does anyone know is this > > possible? Is it a target we build or something like this? Thanks in > > advance, and I'm going to dig into this a bit further myself > > meanwhile. > > > Regards, > > > Michael
