How can I publish my Outlook Addin project from my solution(I don't want to publish all my solution) from command line tools(MSBuild)?
Furthermore I'd like to use TeamCity to publish this OutlookAddin(just this project from solution).
THX.
I think you can find the information you need here;
How to build an Office Add-In without registering it on the build system?
TeamCity supports MSBuild configuration steps, so once you get the MsBuild setup correct, getting TeamCity to build your addin should be straightforward.
Related
Developers use the Visual Studio (VS) GUI to develop their solutions and get their projects all building using a solution file (.SLN). The build teams using vNext then have to automate those builds using MSBuild instead of devenv.exe (the Visual Studio executable file). This is a serious and chronic problem because not only is MSBuild incapable of building several project types, but the build order is defined in a completely different, and complex, way.
Some Microsoft advice (https://learn.microsoft.com/en-us/archive/blogs/msbuild/incorrect-solution-build-ordering-when-using-msbuild-exe) is to switch to explicit dependencies in each .*proj file and remove all dependency specifications in the .SLN file. This sounds like a person who has never worked in a relatively powerless build team trying to get development teams to:
do a lot of what they perceive as time-wasting extra work and to
change how they do things
What build teams need is a way to automate whatever VS allows dev teams to build. If VS is given a SLN to build, then a vNext build needs to be able to use that same SLN in the same way. Instead vNext currently only offers MSBuild as the build tool. MSBuild has many more options than devenv, so that would be great, IF it could be made to use the SLN to govern dependencies in the same way as VS, and would be upgraded to build all the same project types.
There have been prospective efforts, referenced by PatrickLu-MSFT at Build project using devenv.exe in TFS 15RC1 Build Server, to enhance a vNext build step to allow devenv to be used instead of MSBuild, but those efforts seem to have been dropped.
Maybe someone has developed a custom vNext build step to build using devenv?
Here is an existing extension you can reference, which provides a build task in your TFS/VSTS instance that will allow you to build your projects using DevEnv.com (Visual Studio):
https://marketplace.visualstudio.com/items?itemName=mmajcica.devenv-build
If you want to automatically use TFS/DevOps build whatever solution files our development teams get working using Visual Studio, you could set CI trigger in build pipeline, when the solution build successfully on local, you can check in/commit the changes, and trigger TFS/DevOps builds.
Similar to this question, except we are not using TeamCity. The error I receive in TFS is:
The project file "xyz.rptproj" is not supported by MSBuild
and cannot be built.
In our old process (TFS 2013 XAML builds) we had to create a custom build template to call the IDE. I cannot seem to find a way to do this with TFS 2017. Is it as easy as having a PowerShell script call it?
I have a solution in TFS 2015 that using continues integration build method, what i want is every check-in triggers a build that selectively only output changed dlls, exe, into the artifact folder. Is there a such configuration to do so?
Unfortunately, there is no this built-in configuration with vNext build in TFS2015.
However, a obvious solution is adding a Powershell Script on what to publish as artifacts. Using a PowerShell script to organize everything and pre-compressing in single files is the best approach for your situation.
Detail step and screenshot please take a look at this blog: Manage Artifacts with TFS Build vNext
How does one configure the teamcity build process to produce the same compilation result as if I told Visual Studio to publish a website from Visual Studio?
basically, I need teamcity to build the website with a publishable package...then publish the package as an artifact, which I can then deploy on AWS using command line commands.
Is it possible? What are the command line MSBuild parameters necessary to get Visual Studio to spit out what I am looking for, and what would I need to match in the build output in order to publish the package? Currently, the website is too big for me to publish everything as an artifact, so I'm having trouble figuring out what to match for artifact publishing.
You need to build target WebPublish - that's what VS does when you select web project and publish it from context menu.
I am currently using a build definition for continuous integration in TFS 2012.
I am using the following build arguments
/p:DeployOnBuild=true;PublishProfile=DEV_SERVER;Password=secret
and everything works well.
Now I need to publish the build to more than one site, and I have created the publishing profiles in visual studio. But how to tell MSBuild to use more than one profile?
/p:DeployOnBuild=true;PublishProfile=DEV_SERVER1;Password=secret /p:DeployOnBuild=true;PublishProfile=DEV_SERVER2;Password=secret /p:DeployOnBuild=true;PublishProfile=DEV_SERVER3;Password=secret
does not work. Only one site is published. (I'm not sure the first or last)
Does anyone know how to specify?
I know that I can duplicate the build definition on TFS using another profile in this new build definition, but in this case the application will be built TWO times and the releases on the servers have different build numbers.
you can specify publish xml in the MSBuild arguments
/t:Build /t:Publish /p:SqlPublishProfilePath=DEV.publish.xml
also this option only works for TFS2012 and VS2012