Team Foundation Server 2017 Update 3.1 版本資訊 Team Foundation Server 2017 Update 3.1 Release Notes

注意

如果您是從非英文語言版本的頁面存取此頁面,並想查看最新的內容,請瀏覽此版本資訊頁面的英文版本。If you are accessing this page from a non-English language version, and want to see the most up-to-date content, please visit this Release Notes page in English.

提示

您可以在此頁面的底部切換頁面語言。You can switch the page language at the bottom of this page. 按一下Click the 圖示,搜尋您的語言,或從可用語言的清單中選取。 icon, search for your language, or select from the list of available languages.

Download Team Foundation Server 2017 Update 3.1

如需其他格式或語言,請參閱下載網站For other formats or languages, please see the download site.

若要深入了解 Team Foundation Server 2017,請參閱 Team Foundation Server Requirements and Compatibility (Team Foundation Server 需求和相容性) 頁面。To learn more about Team Foundation Server 2017, see the Team Foundation Server Requirements and Compatibility page.


Team Foundation Server 2017 Update 3.1 發行日期:2018 年 2 月 28 日Team Foundation Server 2017 Update 3.1 Release Date: February 28, 2018

Team Foundation Server 2017 Update 3.1 的新功能What's New in Team Foundation Server 2017 Update 3.1

此更新修正潛在的跨網站指令碼 (XSS) 和其他安全性漏洞。This update fixes potential cross site scripting (XSS) and other security vulnerabilities. 如需詳細資訊,請參閱部落格文章 (英文)。See the blog post for more information. 它是完整的升級,因此您可以直接升級至 TFS 2017 Update 3.1。It is a full upgrade, so you can upgrade directly to TFS 2017 Update 3.1.

意見反應Feedback

請提供您的意見!We’d love to hear from you! 您可以透過開發人員社群回報並追蹤問題,並在 Stack Overflow 上取得建議。You can report a problem and track it through Developer Community and get advice on Stack Overflow. 一如往常,如果您對想要看到我們設定優先順序的項目有任何想法,請前往 UserVoice 新增您的想法或對現有想法進行投票。As always, if you have ideas on things you’d like to see us prioritize, head over to UserVoice to add your idea or vote for an existing one.


Team Foundation Server 2017 Update 3 發行日期:2017 年 11 月 6 日Team Foundation Server 2017 Update 3 Release Date: November 6, 2017

Team Foundation Server 2017 Update 3 的新功能What's New in Team Foundation Server 2017 Update 3

這是 Team Foundation Server 2017 的更新,包含自 Team Foundation Server 2017 Update 2 以來的 Bug 修正。This is an update for Team Foundation Server 2017 that includes bug fixes since Team Foundation Server 2017 Update 2.


工作Work

  • 如果範本含有大於 127 的 ASCII 字元碼,匯出時就沒有 WebLayout 且包含不正確的檔案名稱。Exporting a template with ASCII character code >127 does not have WebLayout and includes incorrect file names.
  • 面板和卡的設定無法處理工作項目類型重新命名。Board and Card Settings does not handle Work Item Type rename.
  • 重新排列的土耳其文工作流程看板卡應該按照堆疊順位。Kanban board card reordering in Turkish should be by stack rank.
  • REST API WorkItemSearchConditionalFaultIn 應該針對搜尋擲回 NotSupportedException。REST API WorkItemSearchConditionalFaultIn should throw NotSupportedException for Search.
  • WIT 的 StructureChangeNotification 事件未引發。StructureChangeNotification event not firing for WIT.
  • 當超過最大連結限制時,您可以新增詳細資訊的連結。Add link to more info when exceeding max links limit.
  • 將工作項目欄位資料移轉的執行計畫最佳化,以改進升級效能。Optimize work item field data migration execution plan to improve upgrade performance.
  • [指派至] 操作功能表應使用下拉式字串而不是顯示名稱,以明確指定。Assigned To context menu should use combo string instead of display name to disambiguate.

程式碼Code

  • Maven:現在會產生程式碼涵蓋範圍Maven: Code coverage will now be generated.
  • 在新的總管中,HTML 檔案不會再預設為預覽模式。HTML files will no longer default to Preview mode in the new Explorer.
  • 新增了檢視變更集時的捲軸We have added a scroll bar when viewing changesets.
  • 我們修正了 Web 中的垂直捲動功能 ([程式碼]-> [變更集] 與 [檔案]),現在可在 IE11 / Chrome 中使用We fixed the vertical scrolling in Web (both Code->Changesets as Files) will now work in IE 11/Chrome.
  • 捲動功能現在能在來源總管中使用 (IE/Edge)Scrolling now works in Source Explorer (IE/Edge).
  • 您現在可以針對已離開專案的使用者篩選變更集You can now filter changesets for users who have left the project.
  • 現在您可以選取檔案,然後選回左側樹狀中的根目錄,並維持在全螢幕模式中。You are now able to select a file, then select back in the root directory, of the left tree, and remain in full screen mode.
  • 若有大量存放庫,當搜尋 URL 超出預設支援的長度時,就不會再擲回例外狀況。The search URL will no longer throw an exception when it exceeds the defaulted supported length if there are a large number of repositories.
  • 若 Git 存放庫中沒有任何預設分支,則不再設定檔案資料夾。File folders will no longer be configured if there is no default branch in the Git Repository.
  • 延伸模組的安裝作業不會與先前的延伸模組解除安裝作業產生衝突。Extension installs will not conflict with the jobs of previous extension uninstall operations.
  • 我們已修正搜尋服務,現在即使作業失敗還是可以運作。We fixed Search and it now works despite job failures.
  • 若 Accountfaultin 作業執行超過一次,ReindexingStatus 將不再維持在 Inprogress 狀態下。ReindexingStatus will no longer remain in an Inprogress state if the Accountfaultin job is run more than once.
  • TFVC 搜耙將不再因版本控制 (VC) 權限問題而失敗。TFVC crawl will no longer fail due to version control (VC) permission issues.
  • 在日文組建升級至 TFS 2017 Update 2 之後,搜尋服務函式將不再失敗。The Search function will no longer fail post upgrade to TFS 2017 Update 2 in the Japanese build.
  • 搜尋服務函數不會再像從 TFS Update 1 升級至 TFS Update 2 時一樣失敗。The Search function will no longer fail as it did when upgrading from TFS Update 1 to TFS Update 2.
  • 作業結果訊息現在會提供更多關於編制索引的深入解析。The Job Result message will now give more insights into the indexing.
  • 我們已經降低修補作業失敗次數。We have reduced the Patch operation failure count.
  • 不論作業執行的時間限制為何,TimeBoxed Crawler 都會在至少一個批次編目。TimeBoxed Crawler will now crawl at least one batch irrespective of job execution time limit.
  • 我們已修正失敗檔案的修補作業 KPI,使其與搜尋服務的記錄一致。We fixed patch operation KPIs for failed files to be consistent with logs for Search.
  • 我們已改良 Git for Windows 中的 SSH 通訊協定版本支援。We improved the support for SSH protocol version in Git for Windows.

組建Build

  • 嘗試註冊組建代理程式時發生錯誤:驗證 -「沒有足夠的堆疊可安全地繼續執行此程式。」Error while attempting to register build agent: Authentication - "Insufficient stack to continue executing the program safely."
  • 更新 vsts-agent 以執行新版本的 GitUpdate vsts-agent to carry new version of git.
  • 啟用 NuGet 工具安裝程式工作,以在組建中加入 NuGet.exe 4.3.0,進而達成與 .NET 的相容性。Enable NuGet Tool Installer task in order to allow for NuGet.exe 4.3.0 to be included in builds for compatibility with .NET.
  • 排程的 XAML 組建 RequestedFor 欄位未設定。RequestedFor field of scheduled XAML build is not set.

發行Release

  • 從 TFS 2017 的升級無法將 Azure 型連線服務移轉至服務端點。Upgrade from TFS 2017 failing migration of Azure-based connected service to service endpoint.

測試Test

  • 在 Win7 SP1 電腦上,部署測試代理程式工作有多個問題。Deploy Test Agent task has multiple issues on Win7-SP1 machine.
  • 如果測試代理程式的路徑錯誤,系統不會將其記錄為錯誤,而只會出現在偵錯中。If Test Agent path is wrong it is not logged as error but appears only in debug.
  • 如果我們無法上傳附件,測試執行/工作不應失敗。Test run/task shouldn’t fail if we failed to upload attachment.
  • GetTestPlatform API 會根據設定,在探查目錄中尋找 testplatform.config 檔案。GetTestPlatform API will look for a testplatform.config file in the probing directory based on configuration.
  • 卸除 dbo.tbl_TestResult 上的索引以大幅改善升級效能。Drop indexes on dbo.tbl_TestResult to significantly improve upgrade performance.
  • 改善測試結果移轉維護步驟的效能,以大幅改善升級效能。Improve performance of test results migration servicing step to significantly improve upgrade performance.

報告Reporting

  • RDL 待執行工作報表現在會顯示已刪除工作的正確時間長度。The RDL Burndown Reports will now show the correct amount of time for deleted tasks.

管理Administration

  • 使用者頁面公用 URL 應該與呼叫的 URL 相符,例如在牽涉到負載平衡器時。Users page Public URL should match the calling URL such as when a load balancer is involved.

頁首
Top of Page