TFS 2017 - 版本控制 [英] TFS 2017 - Versioning

查看:115
本文介绍了TFS 2017 - 版本控制的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们的旧XAML构建使用版本种子文件来获取版本信息并将其应用于正在构建的解决方案。  从下面的屏幕截图中可以看出,这非常强大且方便。  我们不仅能够在一个文件中保存所有版本信息
(而不是在每个单独的构建定义中),而且我们还可以将新版本的AssemblyInfo文件签入到源代码管理中。我们也可以将版本控制应用于数据库存储过程。


不幸的是,我不是设置此过程的一部分,现在我们已经转移到2017年的TFS。我希望有2017年的类似选项,以便我们不必在每个单独的构建定义中维护版本。


我已经搜索了可以执行这些任务但没有运气的扩展。  任何想法/想法都将是一个巨大的帮助。  提前谢谢!


解决方案

您好Pauly,


您可以添加一个powershell任务并自定义您自己的脚本以实现您想要的效果。请查看以下博客:


https:/ /intovsts.net/2015/08/24/tfs-build-2015-and-versioning/


祝你好运,


Our old XAML builds used a Version Seed File to get version information and apply it to a solution being built.  As you can see from the screenshot below this was very robust and convenient.  Not only were we able to maintain all our version information in one single file (instead of in each individual build definition) but we could also check-in the newly versioned AssemblyInfo files into Source Control. We could also apply the versioning to a database stored procedure.

Unfortunately, I was not part of setting up this process and now we have moved to TFS 2017.  I am hoping there is a similar option in 2017 so that we do not have to maintain versioning in each individual build definition.

I've already searched for extensions that could perform these tasks with no luck.  Any thoughts/ideas would be a huge help.  Thank you in advance!

解决方案

Hi Pauly,

You may add a powershell task and customize your own script to achieve what you want. Check the blog below:

https://intovsts.net/2015/08/24/tfs-build-2015-and-versioning/

Best regards,


这篇关于TFS 2017 - 版本控制的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆