I'm using Visual Studio 2010 and TFS 2010. Is there a way that dll version be automatically incremented with each TFS build?
Thanks
I have a blog post on how to version your assemblies in TFS Build 2010:
How to Create a Custom Workflow Activity for TFS Build 2010 RTM
Try TfsVersioning build definition. It can be alse extended with Nugetter to create a NuGet package and upload it to a repository.
You can use Version task from msbuildtasks
Here's blog post by Jeremy Jameson with step-by-step instructions on how to use it.
Related
I have a 2010 project that needs built through TFS 2017. I am using the visual studio build task to do this.
The only options I am given to use are VS 2012 - 2017. Is there a way around this?
Visual Studio Build task has automatically set the /p:VisualStudioVersion property for us. And the versions only support VS 2012 - 2017.
The workaround is to use MSBuild task to specify MSBuild 4.0 version or specify the MSBuild location.
You must upgrade your project to use the minimum supported visual studio version on the build task.
After upgrade of Visual Studio 2017 last week on my build server, the MS Build 15.0 is not in use anymore. So whenever I try to compile visual studio 2017 projects which use new feature they will fail.
The Warning in build log is:
Visual Studio version '15.0' not found. Looking for the latest
version.
And the error is:
something.cs(542,41): Error CS1525: Invalid expression term 'int'
Which is because build server is using MS build 14.0 I guess.
So far I have
1- Uninstall and Reinstalled the Visual Studio 2017 on the build server.
2- Installed "Visual Studio Build Tools 2017".
And nothing works.
I have read some articles and apparently there are missing registry values but I don't know how to create them.
Appreciate your helps on this topic.
I am using TFS 2017 SP1 (On premises) and Visual Studio 2017 latest updates.
This may due to the VS is installed after the build agent configured. Then reregister the build agent with TFS, since the system capabilities are only discovered when the agent is first configured -- any changes made after that are not captured.
More ways please refer this similar question: No agent could be found with the following capabilities: msbuild, visualstudio, vstest?
Or install the latest version of the agent for now, which appears to be capable of detecting VS2017.
Also remember to select VS2017 in Visual Studio Version picklist of Visual Studio Build task.
I have resolved this issue by upgrading my TFS from TFS 2017 SP1 to
TFS 2017 SP2.
Thanks to #Patrick-MSFT and #Martin Ullrich for your help.
I have TFS2012 Update 3 server. We have started new VS 2013 project. I need to prepare build server and service. My initial thought is to install Vs 2013 together with TFS2013 build service.
After installation TFS2013 and registration to TFS collection I got below issue:
The register command is not supported for Team Foundation Service [our_tfs_url] because the server is not compatible.
Please advice any solution how to create builds for VS 2013 projects that are stored in TFS 2012.
Update 1:
1) I installed TFS 2012 build service and redirect msbuild ( toolpath) in build template to use VS 2013 msbuild
2) I am able now to build project with a test
3) There are still issue with Code Coverage, that finish with warning: Install visual studio. It seems for me that CC used still VS 2012. Is any way to redirect CC to VS 2013?
Below solution helps me build on VS 2013 build machine with TFS 2012 build service and generate code coverage.
TFS 2012 buid service runs tests from 11.0 location, to replace CommonExtensions in folder
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\CommonExtensions
with Vs 2013 assemblies from
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions
fix that issue and now I can see code coverage per build.
thanks MS to provide workaround on that issue with Code coverage.
Does anyone use Specflow 1.7.0 with Visual Studio Team System 2008? There are no Specflow templates available in “Add New Item” window after installation.
Installed previous version 1.6.1 and this time integration works fine. Any idea?
I have the same problem.
I was thinking it was because of a bad update of the msi version... but no.
Now : I need to create manually a .feature file
edit :
I have installed cuke4vs
https://github.com/henritersteeg/cuke4vs/downloads
now it's possible to to add features with "Add New Item"
(and in addition the feature file is colored :) )
Most probably found the bug.
Install the next nightly build from build.specflow.org, I hope it will work then.
We have a TFS build which outputs 2 exe's for 2 different solutions. How do I now integrate my build with InstallShield to use these exe's of both the solutions in my installer.
Any points to information would be greatly appreciated.
Thanks much in advance!!
There is no "as is" integration for this in TFS/MsBuild. You must open the msbuild script that TFS uses for each of your solutions and specify a target that will launch installshield.
If you use the integrated into VisualStudio version of InstallShield 2011, the setup can be part of the solution. But you have to install the stand alone version of InstallShield on TFS build machine. This done, InstallShield projects are built automatically by TFS, too.