I have a visual studio solution that consists of several web applications, windows services and other class libraries. I am in the process of configuring it for continuous integration with TFS 2010.
A gated check-in will create a change-set whose name is ended with ***NO_CI***? What is that NO_CI stand for? I can just think of \"no check in errors\" but it 开发者_StackOverflow中文版doesn\'t make
This is a feature I\'m used to from TeamCity - I could specify that a certain build configuration will be triggered by the success of another build configuration.
I\'d like to set up a TFS 2008 build in a way that it runs on every check-in and also nightly. The thing is that I\'d like to keep the output from the build only for the nightly builds (with the check
We have moved to Visual Studio 2010 but our TFS folks are not ready yet.After some work, we can get the build to work, but we don\'t get code coverage.
We have customized the build process with a InvokeProcess action that runs a powershell script that deploys our sln.
When queuing a new build开发者_如何学Python using VS it is possible to pass in arguments to MSBuild which let\'s you do thing like skipping some steps of the build or do some things conditionally.
I am using the following MSBuild command form the command prompt: MSBuild.exe /nologo \"Server.Website.csproj\" /T:Package
I\'m attempting to create a 3.5 build from a 4.0 set of code.It almost works the following msbuild options: /tv:3.5 /p:targetframeworkversion=v3.5.The issue is that I get a conflict for those classes
Is there a way to enforce \"Treat warnings as errors\" on the 开发者_如何转开发TFS Build level?I know you can do this on a project by project basis, but need to enforce on the TFS level.No. It\'s alwa
加载中,请稍侯......