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

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

ASP.NETASP.NET

AllowCustomPaging 設為 true 的 GridView 可能在離開檢視的最後一頁時引發 PageIndexChanging 事件GridViews with AllowCustomPaging set to true may fire the PageIndexChanging event when leaving the final page of the view

詳細資料Details

.NET Framework 4.5 中的 Bug) 導致有時不會針對已啟用 System.Web.UI.WebControls.GridView.AllowCustomPagingSystem.Web.UI.WebControls.GridView 引發 System.Web.UI.WebControls.GridView.PageIndexChangingA bug in the .NET Framework 4.5 causes System.Web.UI.WebControls.GridView.PageIndexChanging to sometimes not fire for System.Web.UI.WebControls.GridViews that have enabled System.Web.UI.WebControls.GridView.AllowCustomPaging.

建議Suggestion

此問題在 .NET Framework 4.6 中已修正,因此可藉由升級至該版 .NET Framework 來解決。This issue has been fixed in the .NET Framework 4.6 and may be addressed by upgrading to that version of the .NET Framework. 應用程式可以對叫用這些條件 (System.Web.UI.WebControls.GridView 位在最後一個頁面上且 LastSystem.Web.UI.WebControls.GridView.PageSize 不同於 System.Web.UI.WebControls.GridView.PageSize) 的 Page_Load 執行明確的 BindGrid,來解決這個問題。As a work-around, the app can do an explicit BindGrid on any Page_Load that would hit these conditions (the System.Web.UI.WebControls.GridView is on the last page and LastSystem.Web.UI.WebControls.GridView.PageSize is different from System.Web.UI.WebControls.GridView.PageSize). 或者,可以修改應用程式以允許分頁 (而不是自訂分頁),因為該情況不會顯示此問題。Alternatively, the app can be modified to allow paging (instead of custom paging), as that scenario does not demonstrate the problem.

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

受影響的 APIAffected APIs

核心Core

在 .NET Framework 4.5 中利用 NetDataContractSerializer 序列化過的 ConcurrentDictionary,無法由 .NET Framework 4.5.1 或 4.5.2 還原序列化A ConcurrentDictionary serialized in .NET Framework 4.5 with NetDataContractSerializer cannot be deserialized by .NET Framework 4.5.1 or 4.5.2

詳細資料Details

由於此類型的內部變更,使用 System.Runtime.Serialization.NetDataContractSerializer 以 .NET Framework 4.5 序列化的 ConcurrentDictionary<TKey,TValue> 物件,無法在 .NET Framework 4.5.1 或 .NET Framework 4.5.2 中還原序列化。請注意,反向移動 (以 .NET Framework 4.5.x 序列化並以 .NET Framework 4.5 還原序列化) 則運作正常。Due to internal changes to the type, ConcurrentDictionary<TKey,TValue> objects that are serialized with the .NET Framework 4.5 using the System.Runtime.Serialization.NetDataContractSerializer cannot be deserialized in the .NET Framework 4.5.1 or in the .NET Framework 4.5.2.Note that moving in the other direction (serializing with the .NET Framework 4.5.x and deserializing with the .NET Framework 4.5) works. 同樣地,所有 4.x 跨版本序列化在 .NET Framework 4.6 中都會正常運作。以單一 .NET Framework 版本進行序列化和還原序列化則不受影響。Similarly, all 4.x cross-version serialization works with the .NET Framework 4.6.Serializing and deserializing with a single version of the .NET Framework is not affected.

建議Suggestion

如果必須在 .NET Framework 4.5 和 .NET Framework 4.5.1/4.5.2 之間序列化和還原序列化 System.Collections.Concurrent.ConcurrentDictionary<TKey,TValue>,則應該使用替代的序列化程式 (例如 System.Runtime.Serialization.DataContractSerializerSystem.Runtime.Serialization.Formatters.Binary.BinaryFormatter 序列化程式) 來取代 System.Runtime.Serialization.NetDataContractSerializer。此外,由於此問題已在 .NET Framework 4.6 中解決,因此可藉由升級至該版 .NET Framework 來解決。If it is necessary to serialize and deserialize a System.Collections.Concurrent.ConcurrentDictionary<TKey,TValue> between the .NET Framework 4.5 and .NET Framework 4.5.1/4.5.2, an alternate serializer like the System.Runtime.Serialization.DataContractSerializer or System.Runtime.Serialization.Formatters.Binary.BinaryFormatter serializer should be used instead of the System.Runtime.Serialization.NetDataContractSerializer.Alternatively, because this issue is addressed in the .NET Framework 4.6, it may be solved by upgrading to that version of the .NET Framework.

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

受影響的 APIAffected APIs

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

AppDomainSetup.DynamicBase 不再由 UseRandomizedStringHashAlgorithm 隨機化AppDomainSetup.DynamicBase is no longer randomized by UseRandomizedStringHashAlgorithm

詳細資料Details

在 .NET Framework 4.6 之前,如果已在應用程式組態檔中啟用 UseRandomizedStringHashAlgorithm,DynamicBase 的值就會在應用程式定義域或處理序之間隨機化。Prior to the .NET Framework 4.6, the value of DynamicBase would be randomized between application domains, or between processes, if UseRandomizedStringHashAlgorithm was enabled in the app's config file. 從 .NET Framework 4.6 開始,DynamicBase 將會在執行之應用程式的不同執行個體之間以及不同的應用程式定義域之間,傳回穩定的結果。Beginning in the .NET Framework 4.6, DynamicBase will return a stable result between different instances of an app running, and between different app domains. 動態基底仍會因不同的應用程式而異;這項變更只會移除相同應用程式之不同執行個體的隨機命名項目。Dynamic bases will still differ for different apps; this change only removes the random naming element for different instances of the same app.

建議Suggestion

請注意,啟用 UseRandomizedStringHashAlgorithm 不會導致 DynamicBase 隨機化。Be aware that enabling UseRandomizedStringHashAlgorithm will not result in DynamicBase being randomized. 如果需要隨機基底,必須在您的應用程式程式碼中產生它,而不是透過此 API 產生。If a random base is needed, it must be produced in your app's code rather than via this API.

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

受影響的 APIAffected APIs

如果索引類型可解決語意模糊,在索引子屬性上呼叫 Attribute.GetCustomAttributes 不會再擲回 AmbiguousMatchExceptionCalling Attribute.GetCustomAttributes on an indexer property no longer throws AmbiguousMatchException if the ambiguity can be resolved by index's type

詳細資料Details

在 .NET Framework 4.6 之前,在索引子屬性上呼叫 GetCustomAttribute(s),而且該索引子屬性與其他屬性只有索引類型不同時,會造成 System.Reflection.AmbiguousMatchExceptionPrior to the .NET Framework 4.6, calling GetCustomAttribute(s) on an indexer property which differed from another property only by the type of the index would result in an System.Reflection.AmbiguousMatchException. 從 .NET Framework 4.6 開始,將會正確地傳回屬性 (Property) 的屬性 (Attributee)。Beginning in the .NET Framework 4.6, the property's attributes will be correctly returned.

建議Suggestion

請注意,GetCustomAttribute 現在正常運作的頻率會更高。Be aware that GetCustomAttribute(s) will work more frequently now. 如果應用程式先前依賴 System.Reflection.AmbiguousMatchException,現在應該改用反映來明確尋找多個索引子。If an app was previously relying on the System.Reflection.AmbiguousMatchException, reflection should now be used to explicitly look for multiple indexers, instead.

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

受影響的 APIAffected APIs

分析工具不會列舉 COR_PRF_GC_ROOT_HANDLECOR_PRF_GC_ROOT_HANDLEs are not being enumerated by profilers

詳細資料Details

在 .NET Framework v4.5.1 中,分析 API RootReferences2() 會錯誤地永不傳回 COR_PRF_GC_ROOT_HANDLE (而是傳回為 COR_PRF_GC_ROOT_OTHER)。In the .NET Framework v4.5.1, the profiling API RootReferences2() is incorrectly never returning COR_PRF_GC_ROOT_HANDLE (they are returned as COR_PRF_GC_ROOT_OTHER instead). 從 .NET Framework 4.6 開始,已修正此問題。This issue is fixed beginning in the .NET Framework 4.6.

建議Suggestion

此問題在 .NET Framework 4.6 中已修正,因此可藉由升級至該版 .NET Framework 來解決。This issue has been fixed in the .NET Framework 4.6 and may be addressed by upgrading to that version of the .NET Framework.

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

受影響的 APIAffected APIs

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

ETW EventListeners 無法使用 Explicit 關鍵字從提供者擷取事件 (例如 TPL 提供者)ETW EventListeners do not capture events from providers with explicit keywords (like the TPL provider)

詳細資料Details

具有空白關鍵字遮罩的 ETW EventListeners 無法使用 Explicit 關鍵字從提供者正確地擷取事件。ETW EventListeners with a blank keyword mask do not properly capture events from providers with explicit keywords. 在 .NET Framework 4.5 中,TPL 提供者已開始提供 Explicit 關鍵字並觸發此問題。In the .NET Framework 4.5, the TPL provider began providing explicit keywords and triggered this issue. 在 .NET Framework 4.6 中,已更新 EventListeners,因此不會再發生此問題。In the .NET Framework 4.6, EventListeners have been updated to no longer have this issue.

建議Suggestion

若要解決此問題,請將 EnableEvents(EventSource, EventLevel) 的呼叫取代為 EnableEvents 多載的呼叫,該呼叫明確指定「任何關鍵字」遮罩以使用︰EnableEvents(eventSource, level, unchecked((EventKeywords)0xFFFFffffFFFFffff))。此外,此問題在 .NET Framework 4.6 中已修正,因此可藉由升級至該版 .NET Framework 來解決。To work around this problem, replace calls to EnableEvents(EventSource, EventLevel) with calls to the EnableEvents overload that explicitly specifies the "any keywords" mask to use: EnableEvents(eventSource, level, unchecked((EventKeywords)0xFFFFffffFFFFffff)).Alternatively, this issue has been fixed in the .NET Framework 4.6 and may be addressed by upgrading to that version of the .NET Framework.

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

受影響的 APIAffected APIs

波斯曆現在會使用回教陽曆演算法Persian calendar now uses the Hijri solar algorithm

詳細資料Details

從 .NET Framework 4.6 開始,System.Globalization.PersianCalendar 類別會使用回教陽曆演算法。Starting with the .NET Framework 4.6, the System.Globalization.PersianCalendar class uses the Hijri solar algorithm. 從 .NET Framework 4.6 開始,針對 1800 年以前的日期或 2023 年以後的日期 (西曆),在 System.Globalization.PersianCalendar 與其他日曆之間轉換這些日期可能會產生稍微不同的結果。此外,PersianCalendar.MinSupportedDateTime 現在是 March 22, 0622,而不是 March 21, 0622Converting dates between the System.Globalization.PersianCalendar and other calendars may produce a slightly different result beginning with the .NET Framework 4.6 for dates earlier than 1800 or later than 2023 (Gregorian).Also, PersianCalendar.MinSupportedDateTime is now March 22, 0622 instead of March 21, 0622.

建議Suggestion

請注意,在 .NET Framework 4.6 中使用 PersianCalendar 時,某些較早或較晚的日期可能會稍微不同。Be aware that some early or late dates may be slightly different when using the PersianCalendar in .NET Framework 4.6. 此外,在不同 .NET Framework 版本上執行的處理序之間序列化日期,不會將日期儲存為 PersianCalendar 日期字串 (因為這些值可能不同)。Also, when serializing dates between processes which may run on different .NET Framework versions, do not store them as PersianCalendar date strings (since those values may be different).

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

受影響的 APIAffected APIs

無法再將反映物件從受控程式碼傳遞至跨處理序的 DCOM 用戶端Reflection objects can no longer be passed from managed code to out-of-process DCOM clients

詳細資料Details

無法再將反映物件從 Managed 程式碼傳遞至跨處理序的 DCOM 用戶端。Reflection objects can no longer be passed from managed code to out-of-process DCOM clients. 以下是受到影響的類型:The following types are affected:

呼叫物件的 IMarshal 會傳回 E_NOINTERFACECalls to IMarshal for the object return E_NOINTERFACE.

建議Suggestion

更新封送處理常式代碼以使用非反映物件。Update marshaling code to work with non-reflection objects.

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

受影響的 APIAffected APIs

預設應用程式定義域的 TargetFrameworkName 若未設定,不會再預設為 NullTargetFrameworkName for default app domain no longer defaults to null if not set

詳細資料Details

除非明確設定,否則 System.AppDomainSetup.TargetFrameworkName 之前在預設應用程式定義域中為 Null。The System.AppDomainSetup.TargetFrameworkName was previously null in the default app domain, unless it was explicitly set. 從 4.6 開始,預設應用程式定義域的 System.AppDomainSetup.TargetFrameworkName 屬性會有衍生自 TargetFrameworkAttribute 的預設值 (如果有一個預設值的話)。Beginning in 4.6, the System.AppDomainSetup.TargetFrameworkName property for the default app domain will have a default value derived from the TargetFrameworkAttribute (if one is present). 除非明確遭到覆寫,否則非預設應用程式定義域會繼續從預設應用程式定義域繼承其 System.AppDomainSetup.TargetFrameworkName (在 4.6 中不會預設為 Null)。Non-default app domains will continue to inherit their System.AppDomainSetup.TargetFrameworkName from the default app domain (which will not default to null in 4.6) unless it is explicitly overridden.

建議Suggestion

您應該更新程式碼,讓 TargetFrameworkName 不會預設為 Null。Code should be updated to not depend on TargetFrameworkName defaulting to null. 如果此屬性必須繼續評估為 Null,則可以將它明確設定為該值。If it is required that this property continue to evaluate to null, it can be explicitly set to that value.

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

受影響的 APIAffected APIs

現在,當 .NET 無法處理憑證時,X509Certificate2.ToString(Boolean) 不會擲回例外狀況X509Certificate2.ToString(Boolean) does not throw now when .NET cannot handle the certificate

詳細資料Details

在 .NET Framework 4.5.2 和更早版本中,如果將 true 傳遞給詳細資訊參數,但 .NET Framework 不支援已安裝的憑證時,此方法會擲回例外狀況。In .NET Framework 4.5.2 and earlier versions, this method would throw if true was passed for the verbose parameter and there were certificates installed that weren't supported by the .NET Framework. 現在,此方法會成功,並傳回省略無法存取之憑證部分的有效字串。Now, the method will succeed and return a valid string that omits the inaccessible portions of the certificate.

建議Suggestion

您應該更新所有相依於 X509Certificate2.ToString(Boolean) 的程式碼,以確保傳回字串可在 API 先前擲回例外狀況的特定情況下排除某些憑證資料 (例如公開金鑰、私密金鑰和延伸內容)。Any code depending on X509Certificate2.ToString(Boolean) should be updated to expect that the returned string may exclude some certificate data (such as public key, private key, and extensions) in some cases in which the API would have previously thrown.

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

受影響的 APIAffected APIs

資料Data

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

偵錯工具Debugger

在稍後的步驟中,偵錯工具才會顯示 Null 聯合器值Null coalescer values are not visible in debugger until one step later

詳細資料Details

.NET Framework 4.5 中的 Bug) 會導致在 64 位元版本的 Framework 上執行時,透過 Null 聯合運算設定的值不會立即於執行指派作業之後顯示在偵錯工具中。A bug in the .NET Framework 4.5 causes values set via a null coalescing operation to not be visible in the debugger immediately after the assignment operation is executed when running on the 64-bit version of the Framework.

建議Suggestion

在偵錯工具中逐步執行一段額外時間,將使本機/欄位的值正確更新。Stepping one additional time in the debugger will cause the local/field's value to be correctly updated. 此外,此問題已在 .NET Framework 4.6 中修正;升級至該版 .NET Framework 應可解決此問題。Also, this issue has been fixed in the .NET Framework 4.6; upgrading to that version of the Framework should solve the issue.

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

受影響的 APIAffected APIs

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

全球化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

網路Networking

ContentDisposition DateTimes 會傳回稍微不同的字串ContentDisposition DateTimes returns slightly different string

詳細資料Details

System.Net.Mime.ContentDisposition 的字串表示已更新,從 4.6 開始,一律會以兩個位數表示 System.DateTime 的小時元件。String representations of System.Net.Mime.ContentDisposition's have been updated, beginning in 4.6, to always represent the hour component of a System.DateTime with two digits. 這是為了遵守 RFC822RFC2822This is to comply with RFC822 and RFC2822. 這會導致 ToString() 在 4.6 中傳回稍微不同的字串,例如,當其中一個配置的時間項目早於上午 10:00 時。This causes ToString() to return a slightly different string in 4.6 in scenarios where one of the disposition's time elements was before 10:00 AM. 請注意,ContentDispositions 有時會透過轉換成字串來進行序列化,因此應檢閱任何 ToString() 作業、序列化或 GetHashCode 呼叫。Note that ContentDispositions are sometimes serialized via converting them to strings, so any ToString() operations, serialization, or GetHashCode calls should be reviewed.

建議Suggestion

在不同的 .NET Framework 版本中,ContentDispositions 的字串表示不會正確地相互比較。Do not expect that string representations of ContentDispositions from different .NET Framework versions will correctly compare to one another. 如果可能的話,請將字串轉換回 ContentDispositions,再進行比較。Convert the strings back to ContentDispositions, if possible, before conducting a comparison.

名稱Name Value
範圍Scope MinorMinor
版本Version 4.64.6
類型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

序列化Serialization

DataContract 因未知類型而序列化失敗的例外狀況訊息已變更Exception message has changed for failed DataContract serialization in case of an unknown type

詳細資料Details

從 .NET Framework 4.6 開始,如果 System.Runtime.Serialization.DataContractSerializerSystem.Runtime.Serialization.Json.DataContractJsonSerializer 由於遺漏「已知類型」而無法序列化或還原序列化,則會發出例外狀況訊息。Beginning in the .NET Framework 4.6, the exception message given if a System.Runtime.Serialization.DataContractSerializer or System.Runtime.Serialization.Json.DataContractJsonSerializer fails to serialize or deserialize due to missing 'known types' has been clarified.

建議Suggestion

應用程式不應該相依於特定的例外狀況訊息。Apps should not depend on specific exception messages. 如果應用程式相依於此訊息,請更新它以預期新的訊息,或者 (最好是) 將它變更為只相依於例外狀況類型。If an app depends on this message, either update it to expect the new message or (preferably) change it to depend only on the exception type.

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

受影響的 APIAffected APIs

安裝和部署Setup and Deployment

.NET Framework 4.6 和更新版本中的產品版本變更Product versioning changes in the .NET Framework 4.6 and later versions

詳細資料Details

舊版 .NET Framework (特別是 .NET Framework 4、4.5、4.5.1 和 4.5.2) 的產品版本已變更。Product versioning has changed from the previous releases of the .NET Framework, and particularly from the .NET Framework 4, 4.5, 4.5.1, and 4.5.2. 以下是詳細的變更:The following are the detailed changes:

  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full 機碼中的 Version 項目值已變更為 4.6.xxxxx (.NET Framework 4.6 及其小數點發行版本),以及 4.7.xxxxx (.NET Framework 4.7 和 4.7.1)。The value of the Version entry in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full key has changed to 4.6.xxxxx for the .NET Framework 4.6 and its point releases, and to 4.7.xxxxx for the .NET Framework 4.7 and 4.7.1. 在 .NET Framework 4.5、4.5.1 和 4.5.2 中,其格式為 4.5.xxxxxIn the .NET Framework 4.5, 4.5.1, and 4.5.2, it had the format 4.5.xxxxx.
  • .NET Framework 檔案的檔案和產品版本已從舊版配置 4.0.30319.x 變更為 4.6.X.0 (.NET Framework 4.6 及其小數點發行版本),以及 4.7.X.0 (.NET Framework 4.7 和 4.7.1)。The file and product versioning for .NET Framework files has changed from the earlier versioning scheme of 4.0.30319.x to 4.6.X.0 for the .NET Framework 4.6 and its point releases, and to 4.7.X.0 for the .NET Framework 4.7 and 4.7.1. 當您以滑鼠右鍵按一下檔案後再檢視檔案的屬性時,會看到這些新值。You can see these new values when you view the file's Properties after right-clicking on a file.
  • 受控組件的 AssemblyFileVersionAttributeAssemblyInformationalVersionAttribute 屬性,對於 .NET Framework 4.6 及其小數點發行版本,其 Version 值的格式為 4.6.X.0,對於 .NET Framework 4.7 和 4.7.1,格式則為 4.7.X.0。The AssemblyFileVersionAttribute and AssemblyInformationalVersionAttribute attributes for managed assemblies have Version values in the form 4.6.X.0 for the .NET Framework 4.6 and its point releases, and 4.7.X.0 for the .NET Framework 4.7 and 4.7.1.
  • 在 .NET Framework 4.6、4.6.1、4.6.2、4.7 和 4.7.1 中,Environment.Version 屬性會傳回固定的版本字串 4.0.30319.42000In the .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, and 4.7.1, the Environment.Version property returns the fixed version string 4.0.30319.42000. 在 .NET Framework 4、4.5、4.5.1 和 4.5.2 中,其會以 4.0.30319.xxxxx 格式傳回版本字串 (例如 "4.0.30319.18010")。In the .NET Framework 4, 4.5, 4.5.1, and 4.5.2, it returns version strings in the format 4.0.30319.xxxxx (for example, "4.0.30319.18010"). 請注意,建議應用程式程式碼與 Environment.Version 屬性有任何新的相依性。Note that we do not recommend application code taking any new dependency on the Environment.Version property.
如需詳細資訊,請參閱如何:判斷安裝的 .NET Framework 版本For more information, see How to: Determine which .NET Framework Versions Are Installed.

建議Suggestion

一般而言,應用程式需要具備可偵測 .NET Framework 的執行階段版本和安裝目錄等項目的建議技術:In general, applications should depend on the recommended techniques for detecting such things as the runtime version of the .NET Framework and the installation directory:

  • 若要偵測 .NET Framework 的執行階段版本,請參閱如何:判斷安裝的 .NET Framework 版本To detect the runtime version of the .NET Framework, see How to: Determine Which .NET Framework Versions Are Installed.
  • 若要判斷 .NET Framework 的安裝路徑,請使用 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full 機碼中的 InstallPath 項目值。To determine the installation path for the .NET Framework, use the value of the InstallPath entry in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full key.
[!IMPORTANT] 子機碼名稱是 NET Framework Setup,不是 .NET Framework SetupThe subkey name is NET Framework Setup, not .NET Framework Setup.
  • 若要判斷 .NET Framework Common Language Runtime 的目錄路徑,請呼叫 RuntimeEnvironment.GetRuntimeDirectory() 方法。To determine the directory path to the .NET Framework common language runtime, call the RuntimeEnvironment.GetRuntimeDirectory() method.
  • 若要取得 CLR 版本,請呼叫 RuntimeEnvironment.GetSystemVersion() 方法。To get the CLR version, call the RuntimeEnvironment.GetSystemVersion() method. 針對 .NET Framework 4 及其小數點發行版本 (.NET Framework 4.5、4.5.1、4.5.2 以及 .NET Framework 4.6、4.6.1、4.6.2、4.7 和 4.7.1),該方法會傳回字串 v4.0.30319。For the .NET Framework 4 and its point releases (the .NET Framework 4.5, 4.5.1, 4.5.2, and .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, and 4.7.1), it returns the string v4.0.30319.

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

受影響的 APIAffected APIs

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

.NET Framework 4.6 在登錄中註冊本身時不使用 4.5.x.x 版本The .NET Framework 4.6 does not use a 4.5.x.x version when registering itself in the registry

詳細資料Details

如預期一般,.NET Framework 4.6 在登錄中的版本機碼設定 (位於 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\NET Framework Setup\NDP\v4\Full) 開頭為 '4.6',而不是 '4.5'。As one might expect, the version key set in the registry (at HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\NET Framework Setup\NDP\v4\Full) for the .NET Framework 4.6 begins with '4.6', not '4.5'. 相依於這些登錄機碼以得知電腦上所安裝之 .NET Framework 版本的應用程式應該加以更新,才能了解 4.6 是新的可能版本,以及其與先前的 4.5.x 版相容。Apps that depend on these registry keys to know which .NET Framework versions are installed on a machine should be updated to understand that 4.6 is a new possible version, and one that is compatible with previous 4.5.x releases.

建議Suggestion

藉由尋找 4.5 登錄機碼來更新 .NET Framework 4.5 安裝的應用程式探查,使其也接受 4.6。Update apps probing for a .NET Framework 4.5 install by looking for 4.5 registry keys to also accept 4.6.

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

受影響的 APIAffected APIs

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

工具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.

使用 NETTCP 進行 SSL 安全性和 MD5 憑證驗證的 WCF 服務WCF services that use NETTCP with SSL security and MD5 certificate authentication

詳細資料Details

.NET Framework 4.6 新增了 TLS 1.1 和 TLS 1.2 至 WCF SSL 的預設通訊協定清單。The .NET Framework 4.6 adds TLS 1.1 and TLS 1.2 to the WCF SSL default protocol list. 當用戶端和伺服器電腦安裝 .NET Framework 4.6 或更新版本時,會使用 TLS 1.2 進行交涉。TLS 1.2 不支援 MD5 憑證驗證。When both client and server machines have the .NET Framework 4.6 or later installed, TLS 1.2 is used for negotiation.TLS 1.2 does not support MD5 certificate authentication. 因此,如果客戶使用 MD5 憑證,WCF 用戶端將無法連線到 WCF 服務。As a result, if a customer uses an MD5 certificate, the WCF client will fail to connect to the WCF service.

建議Suggestion

您可以執行下列其中一項動作來解決這個問題,使 WCF 用戶端可以連線到 WCF 伺服器︰You can work around this issue so that a WCF client can connect to a WCF server by doing any of the following:

  • 更新憑證為不使用 MD5 演算法。Update the certificate to not use the MD5 algorithm. 這是建議的解決方案。This is the recommended solution.
  • 如果繫結在原始程式碼中不是以動態方式設定,請更新應用程式的組態檔,以使用 TLS 1.1 或舊版的通訊協定。If the binding is not dynamically configured in source code, update the application's configuration file to use TLS 1.1 or an earlier version of the protocol. 這可讓您繼續使用執行 MD5 雜湊演算法的憑證。This allows you to continue to use a certificate with the MD5 hash algorithm.

警告

我們不建議採取這項因應措施,因為使用 MD5 雜湊演算法的憑證並不安全。This workaround is not recommended, since a certificate with the MD5 hash algorithm is considered insecure.

下列組態檔示範如何進行:The following configuration file does this:

<configuration>
  <system.serviceModel>
    <bindings>
      <netTcpBinding>
        <binding>
          <security mode= "None/Transport/Message/TransportWithMessageCredential" >
            <transport clientCredentialType="None/Windows/Certificate"
                       protectionLevel="None/Sign/EncryptAndSign"
                       sslProtocols="Ssl3/Tls1/Tls11">
            </transport>
          </security>
        </binding>
      </netTcpBinding>
    </bindings>
  </system.ServiceModel>
</configuration>

警告

我們不建議採取這項因應措施,因為使用 MD5 雜湊演算法的憑證並不安全。This workaround is not recommended, since a certificate with the MD5 hash algorithm is considered insecure.

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

受影響的 APIAffected APIs

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

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

從 DataGrid 的 UnloadingRow 事件處理常式存取 WPF DataGrid 的選取項目可能會導致 NullReferenceExceptionAccessing a WPF DataGrid's selected items from a handler of the DataGrid's UnloadingRow event can cause a NullReferenceException

詳細資料Details

由於 .NET Framework 4.5 中的 Bug),涉及移除資料列之 DataGrid 事件的事件處理常式,可能會在它們存取 DataGridSystem.Windows.Controls.Primitives.Selector.SelectedItemSystem.Windows.Controls.Primitives.MultiSelector.SelectedItems 屬性時導致擲回 System.NullReferenceExceptionDue to a bug in the .NET Framework 4.5, event handlers for DataGrid events involving the removal of a row can cause a System.NullReferenceException to be thrown if they access the DataGrid's System.Windows.Controls.Primitives.Selector.SelectedItem or System.Windows.Controls.Primitives.MultiSelector.SelectedItems properties.

建議Suggestion

此問題在 .NET Framework 4.6 中已修正,因此可藉由升級至該版 .NET Framework 來解決。This issue has been fixed in the .NET Framework 4.6 and may be addressed by upgrading to that version of the .NET Framework.

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

受影響的 APIAffected APIs

在已選取項目的 WPF ListBox、ListView 或 DataGrid 上呼叫 Items.Refresh 會導致在項目中出現重複的項目Calling Items.Refresh on a WPF ListBox, ListView, or DataGrid with items selected can cause duplicate items to appear in the element

詳細資料Details

在 .NET Framework 4.5 中,如果 System.Windows.Controls.ListBox 中已選取項目,從程式碼呼叫 ListBox.Items.Refresh 可能會導致選取的項目在清單中重複出現。In the .NET Framework 4.5, calling ListBox.Items.Refresh from code while items are selected in a System.Windows.Controls.ListBox can cause the selected items to be duplicated in the list. System.Windows.Controls.ListViewSystem.Windows.Controls.DataGrid 會發生類似的問題。A similar issue occurs with System.Windows.Controls.ListView and System.Windows.Controls.DataGrid. 這在 .NET Framework 4.6 中已修正。This is fixed in the .NET Framework 4.6.

建議Suggestion

您可以在呼叫 System.Windows.Data.CollectionView.Refresh() 之前以程式設計方式取消選取項目,然後在呼叫完成之後重新選取項目來解決此問題。This issue may be worked around by programmatically unselecting items before System.Windows.Data.CollectionView.Refresh() is called and then re-selecting them after the call is completed. 此外,此問題在 .NET Framework 4.6 中已修正,因此可藉由升級至該版 .NET Framework 來解決。Alternatively, this issue has been fixed in the .NET Framework 4.6 and may be addressed by upgrading to that version of the .NET Framework.

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

受影響的 APIAffected APIs

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

水平捲動和虛擬化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

ObservableCollection<T>.Move 的 ListBoxItem IsSelected 繫結問題ListBoxItem IsSelected binding issue with ObservableCollection<T>.Move

詳細資料Details

針對繫結至 System.Windows.Controls.ListBox 且已選取項目的集合呼叫 Move(Int32, Int32)MoveItem(Int32, Int32),可能會在未來選取或取消選取 System.Windows.Controls.ListBox 項目時導致不穩定的行為。Calling Move(Int32, Int32) or MoveItem(Int32, Int32) on a collection bound to a System.Windows.Controls.ListBox with items selected can lead to erratic behavior with future selection or unselection of System.Windows.Controls.ListBox items.

建議Suggestion

呼叫 System.Collections.ObjectModel.Collection<T>.Remove(T)System.Collections.ObjectModel.Collection<T>.Insert(Int32, T) 而不是 Move(Int32, Int32) 可解決此問題。Calling System.Collections.ObjectModel.Collection<T>.Remove(T) and System.Collections.ObjectModel.Collection<T>.Insert(Int32, T) instead of Move(Int32, Int32) will work around this issue. 此外,此問題在 .NET Framework 4.6 中已修正,因此可藉由升級至該版 .NET Framework 來解決。Alternatively, this issue has been fixed in the .NET Framework 4.6 and may be addressed by upgrading to that version of the .NET Framework.

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

受影響的 APIAffected APIs

以滑鼠右鍵按一下 WPF DataGrid 資料列標頭會變更 DataGrid 選取項目Right clicking on a WPF DataGrid row header changes the DataGrid selection

詳細資料Details

選取多個資料列時,若以滑鼠右鍵按一下選取的 System.Windows.Controls.DataGrid 資料列標頭,會導致 System.Windows.Controls.DataGrid 的選取項目變更為只有該資料列。Right-clicking a selected System.Windows.Controls.DataGrid row header while multiple rows are selected results in the System.Windows.Controls.DataGrid's selection changing to only that row.

建議Suggestion

此問題在 .NET Framework 4.6 中已修正,因此可藉由升級至該版 .NET Framework 來解決。This issue has been fixed in the .NET Framework 4.6 and may be addressed by upgrading to that version of the .NET Framework.

名稱Name Value
範圍Scope EdgeEdge
版本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.

WPF 會繁衍可以凍結滑鼠的 wisptis.exe 處理序WPF spawns a wisptis.exe process which can freeze the mouse

詳細資料Details

在 4.5.2 中產生了一個問題,導致繁衍可凍結滑鼠輸入的 wisptis.exeAn issue was introduced in 4.5.2 that causes wisptis.exe to be spawned that can freeze mouse input.

建議Suggestion

解決此問題的修正程式可在 .NET Framework 4.5.2 的服務版本 (Hotfix 彙總套件 3026376) 中取得,或藉由升級至 .NET Framework 4.6 取得A fix for this issue is available in a servicing release of the .NET Framework 4.5.2 (hotfix rollup 3026376), or by upgrading to the .NET Framework 4.6

名稱Name Value
範圍Scope 主要Major
版本Version 4.5.24.5.2
類型Type 執行階段Runtime

受影響的 APIAffected APIs

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

若語言不在 OS 的輸入語言清單中,啟用文字之控制項中的 WPF 拼字檢查不適用於 Windows 10WPF spell checking in text-enabled controls will not work in Windows 10 for languages not in the OS's input language list

詳細資料Details

因為只有輸入語言清單上的語言可以使用平台拼字檢查功能,所以拼字檢查工具在 Windows 10 上執行時可能不適用於啟用 WPF 文字的控制項。在 Windows 10 中,將語言新增至可用鍵盤的清單時,Windows 會自動下載並安裝對應的 Feature on Demand (FOD) 套件,以提供拼字檢查功能。When running on Windows 10, the spell checker may not work for WPF text-enabled controls because platform spell-checking capabilities are available only for languages present in the input languages list.In Windows 10, when a language is added to the list of available keyboards, Windows automatically downloads and installs a corresponding Feature on Demand (FOD) package that provides spell-checking capabilities. 只要將語言加入輸入語言清單中,就可支援拼字檢查工具。By adding the language to the input languages list, the spell checker will be supported.

建議Suggestion

請注意,要進行拼字檢查的語言或文字必須新增為輸入語言,拼字檢查才能在 Windows 10 中正常運作。Be aware that the language or text to be spell-checked must be added as an input language for spell-checking to work in Windows 10.

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

受影響的 APIAffected APIs

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

WPF 視窗在擴充到單一顯示器之外時呈現而不裁剪WPF windows are rendered without clipping when extending outside a single monitor

詳細資料Details

在 Windows 8 和更新版本中執行的 .NET Framework 4.6 多重監視器案例中,如果視窗擴充到單一顯示畫面之外,可呈現完整視窗而不會將其裁剪。In the .NET Framework 4.6 running on Windows 8 and above, the entire window is rendered without clipping when it extends outside of single display in a multi-monitor scenario. 這與舊版 .NET Framework 不同,後者會在 WPF 視窗擴充到單一顯示畫面之外時裁剪該視窗。This is different from previous versions of the .NET Framework which would clip WPF windows that extended beyond a single display.

建議Suggestion

您可以在應用程式組態檔的 <appSettings> 中使用 <EnableMultiMonitorDisplayClipping> 項目,或在應用程式啟動時藉由設定 EnableMultiMonitorDisplayClipping 屬性,來明確設定這項行為 (不論是否裁剪)。This behavior (whether to clip or not) can be explicitly set using the <EnableMultiMonitorDisplayClipping> element in <appSettings> in an application's configuration file, or by setting the EnableMultiMonitorDisplayClipping property at app startup.

名稱Name Value
範圍Scope MinorMinor
版本Version 4.64.6
類型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.