將執行階段變更從 .NET Framework 4.6 移轉至 4.7.1Runtime Changes for Migration from .NET Framework 4.6 to 4.7.1

如果您想從 .NET Framework 4.6 移轉至 4.7.1,請檢閱下列主題中可能會影響應用程式的應用程式相容性問題:If you are migrating from the .NET Framework 4.6 to 4.7.1, review the following topics for application compatibility issues that may affect your app:

資料Data

嘗試建立 TCP/IP 連線至解析為 localhost 的 SQL Server 資料庫會失敗Attempting a TCP/IP connection to a SQL Server database that resolves to localhost fails

詳細資料Details

在 .NET Framework 4.6 和 4.6.1 中,嘗試建立 TCP/IP 連線至解析為 localhost 的 SQL Server 資料庫會失敗,錯誤為:「建立連線至 SQL Server 時,發生網路相關或執行個體特定的錯誤。In the .NET Framework 4.6 and 4.6.1, attempting a TCP/IP connection to a SQL Server database that resolves to localhost fails with the error, "A network-related or instance-specific error occurred while establishing a connection to SQL Server. 找不到或無法存取伺服器。The server was not found or was not accessible. 檢查執行個體名稱是否正確以及 SQL Server 執行個體是否設定為允許遠端連接。Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (提供者:SQL 網路介面,錯誤:26 - 搜尋指定的伺服器/執行個體時發生錯誤)」(provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)"

建議Suggestion

在 .NET Framework 4.6.2 中已解決此問題,並還原舊版行為。This issue has been addressed and the previous behavior restored in the .NET Framework 4.6.2. 若要連線至解析為 localhost 的 SQL Server 資料庫,請升級至 .NET Framework 4.6.2。To connect to a SQL Server database that resolves to localhost, upgrade to the .NET Framework 4.6.2.

名稱Name Value
範圍Scope MinorMinor
版本Version 4.64.6
類型Type 執行階段Runtime

受影響的 APIAffected APIs

無法透過 API 分析偵測。Not detectable via API analysis.

Azure SQL 資料庫的連線集區封鎖期已移除Connection pool blocking period for Azure SQL databases is removed

詳細資料Details

從 .NET Framework 4.6.2 開始,針對已知 Azure SQL 資料庫的連線開啟要求 (* . database.windows.net、 * database.chinacloudapi.cn、 * database.usgovcloudapi.net、 * database.cloudapi.de) 、已移除連接集區封鎖期間,且未快取連接開啟的錯誤。Starting with the .NET Framework 4.6.2, for connection open requests to known Azure SQL databases (*.database.windows.net, *.database.chinacloudapi.cn, *.database.usgovcloudapi.net, *.database.cloudapi.de), the connection pool blocking period is removed, and connection open errors are not cached. 發生暫時性連線錯誤之後,幾乎會立即嘗試重試連線開啟要求。Attempts to retry connection open requests will occur almost immediately after transient connection errors. 這項變更允許立即重試 Azure SQL Database 的連線開啟嘗試,因而提升啟用雲端功能的應用程式效能。This change allows the connection open attempt to be retried immediately for Azure SQL databases, thereby improving the performance of cloud- enabled apps. 至於所有其他連線嘗試,則會繼續強制執行連線集區封鎖期。For all other connection attempts, the connection pool blocking period continues to be enforced.

在 .NET Framework 4.6.1 和舊版中,如果應用程式在連線到資料庫時發生暫時性連線失敗,由於連線集區會快取此錯誤並在 5 秒鐘到 1 分鐘後重新擲回,因此無法很快就重試連線。In the .NET Framework 4.6.1 and earlier versions, when an app encounters a transient connection failure when connecting to a database, the connection attempt cannot be retried quickly, because the connection pool caches the error and re-throws it for 5 seconds to 1 minute. 如需詳細資訊,請參閱 SQL Server 連線共用 (ADO.NET) (機器翻譯)。For more information, see SQL Server Connection Pooling (ADO.NET). 此行為會對 Azure SQL Database 連線造成問題,連線通常會因暫時性錯誤而失敗,而且一般會在幾秒內復原。This behavior is problematic for connections to Azure SQL databases, which often fail with transient errors that are typically recovered from within a few seconds. 連線集區封鎖功能表示應用程式有很長的一段時間無法連線到資料庫,即使資料庫可供使用且應用程式需要在幾秒內呈現也一樣。The connection pool blocking feature means that the app cannot connect to the database for an extensive period, even though the database is available and the app needs to render within a few seconds.

建議Suggestion

如果不需要這種行為,可以藉由設定 .NET Framework 4.6.2 中引進的 System.Data.SqlClient.SqlConnectionStringBuilder.PoolBlockingPeriod 屬性來設定連線集區封鎖期。If this behavior is undesirable, the connection pool blocking period can be configured by setting the System.Data.SqlClient.SqlConnectionStringBuilder.PoolBlockingPeriod property introduced in the .NET Framework 4.6.2. 屬性的值是 System.Data.SqlClient.PoolBlockingPeriod 列舉的成員,可以採用三個值的其中一個值︰The value of the property is a member of the System.Data.SqlClient.PoolBlockingPeriod enumeration that can take either of three values:

System.Data.SqlClient.SqlConnectionStringBuilder.PoolBlockingPeriod 屬性設為 AlwaysBlock 可以還原舊有行為。The previous behavior can be restored by setting the System.Data.SqlClient.SqlConnectionStringBuilder.PoolBlockingPeriod property to AlwaysBlock.

名稱Name Value
範圍Scope MinorMinor
版本Version 4.6.24.6.2
類型Type 執行階段Runtime

受影響的 APIAffected APIs

全球化Globalization

現在支援 Unicode 標準 8.0 版分類Unicode standard version 8.0 categories now supported

詳細資料Details

在 .NET Framework 4.6.2 中,Unicode 資料已從 Unicode 標準 6.3 版升級至 8.0 版。In .NET Framework 4.6.2, Unicode data has been upgraded from Unicode Standard version 6.3 to version 8.0. 在 .NET Framework 4.6.2 中要求 Unicode 字元分類時,某些結果可能不符合舊版 .NET Framework 中的結果。When requesting Unicode character categories in .NET Framework 4.6.2, some results might not match the results in previous .NET Framework versions. 這項變更主要會影響柴羅基文音節和新傣文母音符號和音調標記。This change mostly affects Cherokee syllables and New Tai Lue vowels signs and tone marks.

建議Suggestion

請檢閱程式碼,並移除/變更仰賴硬式編碼的 Unicode 字元分類的邏輯。Review code and remove/change logic that depends on hard-coded Unicode character categories.

名稱Name Value
範圍Scope MinorMinor
版本Version 4.6.24.6.2
類型Type 執行階段Runtime

受影響的 APIAffected APIs

安全性Security

RSACng.VerifyHash 現在會針對任何驗證失敗傳回 FalseRSACng.VerifyHash now returns False for any verification failure

詳細資料Details

從 .NET Framework 4.6.2 開始,如果簽章本身的格式不正確,此方法會傳回 FalseStarting with the .NET Framework 4.6.2, this method returns False if the signature itself is badly formatted. 現在任何驗證失敗都會傳回 False。在 .NET Framework 4.6 和 4.6.1 中,如果簽章本身的格式不正確,此方法會擲回 System.Security.Cryptography.CryptographicExceptionIt now returns false for any verification failure.In the .NET Framework 4.6 and 4.6.1, the method throws a System.Security.Cryptography.CryptographicException if the signature itself is badly formatted.

建議Suggestion

如果驗證失敗且此方法傳回 False,應改為執行任何仰賴處理 System.Security.Cryptography.CryptographicException 來執行的程式碼。Any code whose execution depends on handling the System.Security.Cryptography.CryptographicException should instead execute if validation fails and the method returns False.

名稱Name Value
範圍Scope MinorMinor
版本Version 4.6.24.6.2
類型Type 執行階段Runtime

受影響的 APIAffected APIs

SignedXml 和 EncryptedXml 重大變更SignedXml and EncryptedXml Breaking Changes

詳細資料Details

在 .NET Framework 4.6.2 中,System.Security.Cryptography.Xml.SignedXmlSystem.Security.Cryptography.Xml.EncryptedXml 的安全性修正會導致不同的執行階段行為。In .NET Framework 4.6.2, Security fixes in System.Security.Cryptography.Xml.SignedXml and System.Security.Cryptography.Xml.EncryptedXml lead to different run-time behaviors. 例如,For example,

  • 如果文件具有包含相同 id 屬性的多個項目,且簽章將目標設為這些項目之一以作為簽章的根項目,該文件現在會視為無效。If a document has multiple elements with the same id attribute and a signature targets one of those elements as the root of the signature, the document will now be considered invalid.
  • 在參考中使用非標準 XPath 轉換演算法的文件現在都視為無效。Documents using non-canonical XPath transform algorithms in references are now considered invalid.
  • 在參考中使用非標準 XSLT 轉換演算法的文件現在會視為無效。Documents using non-canonical XSLT transform algorithms in references are now consider invalid.
  • 任何使用外部資源中斷簽章的程式都無法這麼做。Any program making use of external resource detached signatures will be unable to do so.

建議Suggestion

開發人員可能想要檢閱 XmlDsigXsltTransformXmlDsigXsltTransform,以及衍生自 Transform 之類型的使用方式,因為文件收件者可能無法處理它。Developers might want to review the usage of XmlDsigXsltTransform and XmlDsigXsltTransform, as well as types derived from Transform since a document receiver may not be able to process it.

名稱Name Value
範圍Scope MinorMinor
版本Version 4.6.24.6.2
類型Type 執行階段Runtime

受影響的 APIAffected APIs

工具Tools

Contract.Invariant 或 Contract.Requires<TException> 不會將 String.IsNullOrEmpty 視為 pureContract.Invariant or Contract.Requires<TException> do not consider String.IsNullOrEmpty to be pure

詳細資料Details

針對以 .NET Framework 4.6.1 為目標的應用程式,如果的非變異合約 Contract.Invariant 或呼叫方法的前置條件合約 Requires ,重寫器 String.IsNullOrEmpty 會發出編譯器警告 CC1036:偵測 " 到方法 ' System.string. IsNullOrWhiteSpace (system.string) ' 的呼叫,但方法中沒有 [純]。 " 這是編譯器警告,而不是編譯器錯誤。For apps that target the .NET Framework 4.6.1, if the invariant contract for Contract.Invariant or the precondition contract for Requires calls the String.IsNullOrEmpty method, the rewriter emits compiler warning CC1036: "Detected call to method 'System.String.IsNullOrWhiteSpace(System.String)' without [Pure] in method." This is a compiler warning rather than a compiler error.

建議Suggestion

GitHub 問題 #339 中已解決這種行為。This behavior was addressed in GitHub Issue #339. 若要移除這個警告,您可以從 GitHub 下載並編譯程式碼合約工具原始程式碼的更新版本。To eliminate this warning, you can download and compile an updated version of the source code for the Code Contracts tool from GitHub. 您可以在頁面底部找到下載資訊。Download information is found at the bottom of the page.

名稱Name Value
範圍Scope MinorMinor
版本Version 4.6.14.6.1
類型Type 執行階段Runtime

受影響的 APIAffected APIs

Windows Communication Foundation (WCF)Windows Communication Foundation (WCF)

從 WCF TransportDefaults 中移除 SSL3Remove Ssl3 from the WCF TransportDefaults

詳細資料Details

當使用 NetTcp 搭配傳輸安全性和憑證類型的認證時,SSL 3 通訊協定已不再是用來交涉安全連接的預設通訊協定。When using NetTcp with transport security and a credential type of certificate, the SSL 3 protocol is no longer a default protocol used for negotiating a secure connection. 在大部分情況下,應該不會影響現有的應用程式,因為 TLS 1.0 一律包含在 NetTcp 的通訊協定清單中。In most cases there should be no impact to existing apps as TLS 1.0 has always been included in the protocol list for NetTcp. 所有現有的用戶端應該能夠使用至少 TLS 1.0 來交涉連接。All existing clients should be able to negotiate a connection using at least TLS1.0.

建議Suggestion

如果需要 SSL3,請使用下列組態機制其中之一,將 SSL3 新增至交涉通訊協定的清單。If Ssl3 is required, use one of the following configuration mechanisms to add Ssl3 to the list of negotiated protocols.

NameName Value
範圍Scope EdgeEdge
版本Version 4.6.24.6.2
類型Type 執行階段Runtime

受影響的 APIAffected APIs

如果 addressHeader 項目為 Null,WCF AddressHeaderCollection 現在會擲回 ArgumentExceptionWCF AddressHeaderCollection now throws an ArgumentException if an addressHeader element is null

詳細資料Details

從 .NET Framework 4.7.1 開始,如果其中一個項目是 nullAddressHeaderCollection(IEnumerable<AddressHeader>) 建構函式會擲回 ArgumentExceptionStarting with the .NET Framework 4.7.1, the AddressHeaderCollection(IEnumerable<AddressHeader>) constructor throws an ArgumentException if one of the elements is null. 在 .NET Framework 4.7 和舊版中,不會擲回任何例外狀況。In the .NET Framework 4.7 and earlier versions, no exception is thrown.

建議Suggestion

如果您在 .NET Framework 4.7.1 或更新版本上遇到這項變更的相容性問題,您可以將下列程式程式碼新增至 app.config 檔的區段,以退出宣告 <runtime>If you encounter compatibility issues with this change on the .NET Framework 4.7.1 or a later version, you can opt-out of it by adding the following line to the <runtime> section of the app.config file:

<configuration>
  <runtime>
    <AppContextSwitchOverrides value="Switch.System.ServiceModel.DisableAddressHeaderCollectionValidation=true" />
  </runtime>
</configuration>
NameName Value
範圍Scope MinorMinor
版本Version 4.7.14.7.1
類型Type 執行階段Runtime

受影響的 APIAffected APIs

WCF MsmqSecureHashAlgorithm 預設值現在是 SHA256WCF MsmqSecureHashAlgorithm default value is now SHA256

詳細資料Details

從 .NET Framework 4.7.1 開始,WCF 中用於 Msmq 訊息的預設訊息簽署演算法是 SHA256。Starting with the .NET Framework 4.7.1, the default message signing algorithm in WCF for Msmq messages is SHA256. 在 .NET Framework 4.7 和舊版中,預設的訊息簽署演算法是 SHA1。In the .NET Framework 4.7 and earlier versions, the default message signing algorithm is SHA1.

建議Suggestion

如果您在 .NET Framework 4.7.1 或更新版本上遇到這項變更的相容性問題,您可以在 app.config 檔案的區段中加入下列這一行,以退出宣告變更 <runtime>If you run into compatibility issues with this change on the .NET Framework 4.7.1 or later, you can opt-out the change by adding the following line to the <runtime> section of your app.config file:

<configuration>
  <runtime>
    <AppContextSwitchOverrides value=&quot;Switch.System.ServiceModel.UseSha1InMsmqEncryptionAlgorithm=true&quot; />
  </runtime>
</configuration>
NameName Value
範圍Scope MinorMinor
版本Version 4.7.14.7.1
類型Type 執行階段Runtime

受影響的 APIAffected APIs

無法透過 API 分析偵測。Not detectable via API analysis.

WCF PipeConnection.GetHashAlgorithm 現在會使用 SHA256WCF PipeConnection.GetHashAlgorithm now uses SHA256

詳細資料Details

從 .NET Framework 4.7.1 開始,Windows Communication Foundation 會使用 SHA256 雜湊來產生具名管道的隨機名稱。Starting with the .NET Framework 4.7.1, Windows Communication Foundation uses a SHA256 hash to generate random names for named pipes. 在 .NET Framework 4.7 和舊版中,它已使用 SHA1 雜湊。In the .NET Framework 4.7 and earlier versions, it used a SHA1 hash.

建議Suggestion

如果在 .NET Framework 4.7.1 或更新版本上遇到這項變更的相容性問題,您可以在 app.config 檔案的 <runtime> 區段中新增下列程式行來退出變更:If you run into compatibility issue with this change on the .NET Framework 4.7.1 or later, you can opt-out it by adding the following line to the <runtime> section of your app.config file:

<configuration>
  <runtime>
    <AppContextSwitchOverrides value="Switch.System.ServiceModel.UseSha1InPipeConnectionGetHashAlgorithm=true" />
  </runtime>
</configuration>
NameName Value
範圍Scope MinorMinor
版本Version 4.7.14.7.1
類型Type 執行階段Runtime

受影響的 APIAffected APIs

無法透過 API 分析偵測。Not detectable via API analysis.

Windows Presentation Foundation (WPF)Windows Presentation Foundation (WPF)

StaysOpen=False 時的鏈結快顯視窗Chained Popups with StaysOpen=False

詳細資料Details

當您按一下 StaysOpen=False 快顯視窗的外部時,該快顯視窗應該要關閉。A Popup with StaysOpen=False is supposed to close when you click outside the Popup. 當兩個或多個這類快顯視窗鏈結在一起 (也就是其中一個包含另一個) 時,會發生許多問題,包括:When two or more such Popups are chained (i.e. one contains another), there were many problems, including:

  • 開啟兩個層級,按一下 P2 外部 (但在 P1 內部)。Open two levels, click outside P2 but inside P1. 沒有發生任何事。Nothing happens.
  • 開啟兩個層級,按一下 P1 外部。Open two levels, click outside P1. 這兩個快顯視窗會關閉。Both popups close.
  • 開啟及關閉兩個層級。Open and close two levels. 然後嘗試再次開啟 P2。Then try to open P2 again. 沒有發生任何事。Nothing happens.
  • 嘗試開啟三個層級。Try to open three levels. 你無此權限。You can't. (不會發生任何事,或是前兩個層級關閉,視您按一下的位置而定。 ) 這些案例 (和其他變異) 現在可如預期般運作。(Either nothing happens or the first two levels close, depending on where you click.) These cases (and other variants) now work as expected.

名稱Name Value
範圍Scope EdgeEdge
版本Version 4.7.14.7.1
類型Type 執行階段Runtime

受影響的 APIAffected APIs

變更 TextBlock 控制項之父代的 IsEnabled 屬性會影響任何子控制項Changing the IsEnabled property of the parent of a TextBlock control affects any child controls

詳細資料Details

從 .NET Framework 4.6.2 開始,變更 System.Windows.Controls.TextBlock 控制項之父代的 System.Windows.UIElement.IsEnabled 屬性,會影響 System.Windows.Controls.TextBlock 控制項的任何子控制項 (例如超連結和按鈕)。在 .NET Framework 4.6.1 和舊版中,System.Windows.Controls.TextBlock 內的控制項不一定會反映 System.Windows.Controls.TextBlock 父代的 System.Windows.UIElement.IsEnabled 屬性狀態。Starting with the .NET Framework 4.6.2, changing the System.Windows.UIElement.IsEnabled property of the parent of a System.Windows.Controls.TextBlock control affects any child controls (such as hyperlinks and buttons) of the System.Windows.Controls.TextBlock control.In the .NET Framework 4.6.1 and earlier versions, controls inside a System.Windows.Controls.TextBlock did not always reflect the state of the System.Windows.UIElement.IsEnabled property of the System.Windows.Controls.TextBlock parent.

建議Suggestion

無。None. 這項變更符合 System.Windows.Controls.TextBlock 控制項內的之控制項的預期行為。This change conforms to the expected behavior for controls inside a System.Windows.Controls.TextBlock control.

名稱Name Value
範圍Scope MinorMinor
版本Version 4.6.24.6.2
類型Type 執行階段Runtime

受影響的 APIAffected APIs

CoerceIsSelectionBoxHighlightedCoerceIsSelectionBoxHighlighted

詳細資料Details

涉及 System.Windows.Controls.ComboBox 及其資料來源的特定動作順序會導致 System.NullReferenceExceptionCertain sequences of actions involving a System.Windows.Controls.ComboBox and its data source can result in a System.NullReferenceException.

建議Suggestion

可能的話,請升級至 .NET Framework 4.6.2。If possible, upgrade to .NET Framework 4.6.2.

名稱Name Value
範圍Scope MinorMinor
版本Version 4.64.6
類型Type 執行階段Runtime

受影響的 APIAffected APIs

水平捲動和虛擬化Horizontal scrolling and virtualization

詳細資料Details

此變更會套用至以正交於主要捲動方向之方向執行自身虛擬化的 System.Windows.Controls.ItemsControl (主要範例是 EnableColumnVirtualization="True" 的 System.Windows.Controls.DataGrid)。This change applies to an System.Windows.Controls.ItemsControl that does its own virtualization in the direction orthogonal to the main scrolling direction (the chief example is System.Windows.Controls.DataGrid with EnableColumnVirtualization="True"). 某些水平捲動作業的結果已變更,產生的結果更直覺,且更類似於可比較的垂直作業的結果。The outcome of certain horizontal scrolling operations has been changed to produce results that are more intuitive and more analogous to the results of comparable vertical operations.

這些作業包括 [捲動至此處] 和 [右邊緣],以使用以滑鼠右鍵按一下水平捲軸所取得之功能表中的名稱。The operations include "Scroll Here" and "Right Edge", to use the names from the menu obtained by right-clicking a horizontal scrollbar. 這兩個都會計算候選位移並呼叫 SetHorizontalOffset(Double)Both of these compute a candidate offset and call SetHorizontalOffset(Double).

捲動至新的位移後,「此處」或「右邊緣」的定義可能已變更,因為最近取消虛擬化的內容已變更 System.Windows.Controls.Primitives.IScrollInfo.ExtentWidth 的值。After scrolling to the new offset, the notion of "here" or "right edge" may have changed because newly de-virtualized content has changed the value of System.Windows.Controls.Primitives.IScrollInfo.ExtentWidth.

在 .NET Framework 4.6.2 之前,捲軸作業會直接使用候選位移,即使它可能已不再是「此處」或位於「右邊緣」。Prior to .NET Framework 4.6.2, the scroll operation simply uses the candidate offset, even though it may not be "here" or at the "right edge" any more. 這會導致類似捲動指標「反彈」的效果,以範例來說明最為合適。This results in effects like "bouncing" the scroll thumb, best illustrated by example. 假設 System.Windows.Controls.DataGrid 具有 ExtentWidth=1000 和 Width=200。Suppose a System.Windows.Controls.DataGrid has ExtentWidth=1000 and Width=200. 捲動到「右邊緣」會使用候選位移 1000 - 200 = 800。A scroll to "Right Edge" uses candidate offset 1000 - 200 = 800. 捲動到該位移時,新的資料行會取消虛擬化;假設它們非常寬,因此 System.Windows.Controls.Primitives.IScrollInfo.ExtentWidth 變更為 2000。While scrolling to that offset, new columns are de- virtualized; let's suppose they are very wide, so that the System.Windows.Controls.Primitives.IScrollInfo.ExtentWidth changes to 2000. 捲軸在 HorizontalOffset=800 結束,而指標會「反彈」回到捲軸中央附近,精確來說是在 800/2000 等於 40% 的位置。The scroll ends with HorizontalOffset=800, and the thumb "bounces" back to near the middle of the scrollbar - precisely at 800/2000 = 40%.

發生這種情況時,變更是重新計算新的候選位移,然後再試一次。The change is to recompute a new candidate offset when this situation occurs, and try again. (這是垂直捲動目前運作的方式)。(This is how vertical scrolling works already.)

此變更會為使用者產生更為可預測且直覺式的體驗,但它會影響依賴 System.Windows.Controls.Primitives.IScrollInfo.HorizontalOffset 於水平捲動後 (無論是由使用者叫用或是明確呼叫 SetHorizontalOffset(Double)) 之確切值的所有應用程式。The change produces a more predictable and intuitive experience for the end user, but it could also affect any app that depends on the exact value of System.Windows.Controls.Primitives.IScrollInfo.HorizontalOffset after a horizontal scroll, whether invoked by the end user or by an explicit call to SetHorizontalOffset(Double).

建議Suggestion

在因為取消虛擬化而可能變更 System.Windows.Controls.Primitives.IScrollInfo.ExtentWidth 的任何水平捲動之後,為 System.Windows.Controls.Primitives.IScrollInfo.HorizontalOffset 使用預測值的應用程式應該改為擷取實際值 (以及 System.Windows.Controls.Primitives.IScrollInfo.ExtentWidth 的值)。An app that uses a predicted value for System.Windows.Controls.Primitives.IScrollInfo.HorizontalOffset should be changed to fetch the actual value (and the value of System.Windows.Controls.Primitives.IScrollInfo.ExtentWidth) after any horizontal scroll that could change System.Windows.Controls.Primitives.IScrollInfo.ExtentWidth due to de-virtualization.

名稱Name Value
範圍Scope MinorMinor
版本Version 4.6.24.6.2
類型Type 執行階段Runtime

受影響的 APIAffected APIs

Items.Clear 不會從 SelectedItems 移除重複項目Items.Clear does not remove duplicates from SelectedItems

詳細資料Details

假設選取器 (啟用了多個選取項目) 在其 System.Windows.Controls.Primitives.MultiSelector.SelectedItems 集合中有重複項目 - 相同的項目出現一次以上。Suppose a Selector (with multiple selection enabled) has duplicates in its System.Windows.Controls.Primitives.MultiSelector.SelectedItems collection - the same item appears more than once. 從資料來源移除這些項目 (例如,藉由呼叫 Items.Clear) 無法從 System.Windows.Controls.Primitives.MultiSelector.SelectedItems 中加以移除;只會移除第一個執行個體。Removing those items from the data source (e.g. by calling Items.Clear) fails to remove them from System.Windows.Controls.Primitives.MultiSelector.SelectedItems; only the first instance is removed. 此外,後續使用 System.Windows.Controls.Primitives.MultiSelector.SelectedItems (例如 SelectedItems.Clear()) 可能會發生像是 System.ArgumentException 的問題,因為 System.Windows.Controls.Primitives.MultiSelector.SelectedItems 包含已不在資料來源中的項目。Furthermore, subsequent use of System.Windows.Controls.Primitives.MultiSelector.SelectedItems (e.g. SelectedItems.Clear()) can encounter problems such as System.ArgumentException, because System.Windows.Controls.Primitives.MultiSelector.SelectedItems contains items that are no longer in the data source.

建議Suggestion

如有可能,請升級至 .NET Framework 4.6.2。Upgrade if possible to .NET Framework 4.6.2.

名稱Name Value
範圍Scope MinorMinor
版本Version 4.54.5
類型Type 執行階段Runtime

受影響的 APIAffected APIs

WPF 列印堆疊更新WPF Printing Stack Update

詳細資料Details

使用 System.Printing.PrintQueue 的 WPF 列印 API 現在會呼叫 Windows 的列印文件套件 API,以支援目前已淘汰的 XPS 列印 API。WPF's Printing APIs using System.Printing.PrintQueue now call Window's Print Document Package API in favor of the now deprecated XPS Print API. 進行這項變更是考慮到服務能力;使用者和開發人員都不應該會看到行為或 API 使用方式中有任何變更。The change was made with serviceability in mind; neither users nor developers should see any changes in behavior or API usage. 在 Windows 10 Creators Update 中執行時,預設會啟用新的列印堆疊。The new printing stack is enabled by default when running in Windows 10 Creators Update. 舊版 Windows 上的舊列印堆疊仍會繼續如往常一般運作。The old printing stack will still continue to work just as before in older Windows versions.

建議Suggestion

若要在 Windows 10 Creators Update 中使用舊堆疊,請將 HKEY_CURRENT_USER\Software\Microsoft.NETFramework\Windows Presentation Foundation\Printing 登錄機碼的 UseXpsOMPrinting REG_DWORD 值設為 1To use the old stack in Windows 10 Creators Update, set the UseXpsOMPrinting REG_DWORD value of the HKEY_CURRENT_USER\Software\Microsoft.NETFramework\Windows Presentation Foundation\Printing registry key to 1.

名稱Name Value
範圍Scope EdgeEdge
版本Version 4.74.7
類型Type 執行階段Runtime

受影響的 APIAffected APIs

無法透過 API 分析偵測。Not detectable via API analysis.

Windows Workflow Foundation (WF)Windows Workflow Foundation (WF)

在某些情況下,工作流程現在會擲回原始例外狀況,而不是 NullReferenceExceptionWorkflow now throws original exception instead of NullReferenceException in some cases

詳細資料Details

在 .NET Framework 4.6.2 和舊版中,工作流程活動的 Execute 方法擲回 Message 屬性為 null 值的例外狀況時,System.Activities 工作流程執行階段會擲回 System.NullReferenceException,進而遮罩原始的例外狀況。在 .NET Framework 4.7 中,會擲回之前遮罩的例外狀況。In the .NET Framework 4.6.2 and earlier versions, when the Execute method of a workflow activity throws an exception with a null value for the Message property, the System.Activities Workflow runtime throws a System.NullReferenceException, masking the original exception.In the .NET Framework 4.7, the previously masked exception is thrown.

建議Suggestion

如果您的程式碼依賴處理 System.NullReferenceException,請將它變更為攔截可能會從自訂活動擲回的例外狀況。If your code relies on handling the System.NullReferenceException, change it to catch the exceptions that could be thrown from your custom activities.

名稱Name Value
範圍Scope MinorMinor
版本Version 4.74.7
類型Type 執行階段Runtime

受影響的 APIAffected APIs

工作流程 SQL 持續性會新增叢集主索引鍵,且在某些資料行中不允許有 Null 值Workflow SQL persistence adds primary key clusters and disallows null values in some columns

詳細資料Details

從 .NET Framework 4.7 開始,SqlWorkflowInstanceStoreSchema.sql 指令碼針對 SQL 工作流程執行個體存放區 (SWIS) 所建立的資料表使用叢集主索引鍵。Starting with the .NET Framework 4.7, the tables created for the SQL Workflow Instance Store (SWIS) by the SqlWorkflowInstanceStoreSchema.sql script use clustered primary keys. 因此,識別不支援 null 值。Because of this, identities do not support null values. SWIS 的作業不會受到這項變更影響。The operation of SWIS is not impacted by this change. 已進行更新以支援 SQL Server 異動複寫。The updates were made to support SQL Server Transactional Replication.

建議Suggestion

必須將 SQL 檔案 SqlWorkflowInstanceStoreSchemaUpgrade.sql 套用到現有安裝,才能體驗這項變更。The SQL file SqlWorkflowInstanceStoreSchemaUpgrade.sql must be applied to existing installations in order to experience this change. 新的資料庫安裝將會自動進行此變更。New database installations will automatically have the change.

名稱Name Value
範圍Scope EdgeEdge
版本Version 4.74.7
類型Type 執行階段Runtime

受影響的 APIAffected APIs

無法透過 API 分析偵測。Not detectable via API analysis.