jprdonnelly/dotnet
1
0
Fork 0
mirror of https://github.com/microsoft/dotnet.git synced 2025-12-25 10:00:04 -05:00
Code Issues Projects Releases Wiki Activity

Remove [More Information] links that lead to page with same information

Browse Source
This commit is contained in:
Connie Yau
2017-04-21 08:32:52 -07:00
parent 3bc280dda2
commit 90d1f05fa9
83 changed files with 40 additions and 195 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Documentation/compatibility/a-concurrentdictionary-serialized-in-_net-4_5-with-netdatacontractserializer-cannot-be-deserialized-by-_net-4_5_1-or-4_5_2.md
View File

@@ -36,8 +36,6 @@ Alternatively, because this issue is addressed in the .NET Framework 4.6, it may
### Category
Core
[More information](https://msdn.microsoft.com/en-us/library/dn458360(v=vs.110).aspx#Core)
<!--
### Notes
Should be fairly easy to detect ConcurrentDictionary objects being serialized/deserialized by a NetDataContractSerializer.

4
Documentation/compatibility/application_filtermessage-no-longer-throws-for-re-entrant-implementations-of-imessagefilter_prefiltermessage.md
View File

@@ -38,7 +38,7 @@ Framework 4.6.1.
Apps targeting the .NET Framework 4.6.1 can opt out of this change (or apps
targeting older Frameworks may opt in) by using the
[DontSupportReentrantFilterMessage](https://msdn.microsoft.com/en-us/library/mt620032%28v=vs.110%29.aspx)
[DontSupportReentrantFilterMessage](https://docs.microsoft.com/en-us/dotnet/articles/framework/migration-guide/mitigation-custom-imessagefilter-prefiltermessage-implementations#mitigation)
compatibility switch.
### Affected APIs
@@ -47,8 +47,6 @@ compatibility switch.
### Category
Windows Forms
[More information](https://msdn.microsoft.com/en-us/library/mt620031%28v=vs.110%29.aspx#WinForms)
<!--
### Notes
It's unclear if this one will be better analyzed by Application.FilterMessage callers (who would have seen the exception previously)

12
Documentation/compatibility/apps-published-with-clickonce-that-use-a-sha-256-code-signing-certificate-may-fail-on-windows-2003.md
View File

@@ -13,18 +13,18 @@ Edge
Available
### Change Description
The executable is signed with SHA256. Previously, it was signed with SHA1 regardless of whether the code-signing certificate was SHA-1 or SHA-256. This applies to:
The executable is signed with SHA256. Previously, it was signed with SHA1 regardless of whether the code-signing certificate was SHA-1 or SHA-256. This applies to:
- All applications built with Visual Studio 2012 or later.
- Applications built with Visual Studio 2010 or earlier on systems with the .NET Framework 4.5 present.
- All applications built with Visual Studio 2012 or later.
- Applications built with Visual Studio 2010 or earlier on systems with the .NET Framework 4.5 present.
In addition, if the .NET Framework 4.5 or later is present, the ClickOnce manifest is also signed with SHA-256 for SHA-256 certificates regardless of the .NET Framework version against which it was compiled.
In addition, if the .NET Framework 4.5 or later is present, the ClickOnce manifest is also signed with SHA-256 for SHA-256 certificates regardless of the .NET Framework version against which it was compiled.
- [ ] Quirked
- [x] Build-time break
### Recommended Action
The change in signing the ClickOnce executable affects only Windows Server 2003 systems; they require that KB 938397 be installed.
The change in signing the ClickOnce executable affects only Windows Server 2003 systems; they require that KB 938397 be installed.
The change in signing the manifest with SHA-256 even when an app targets the .NET Framework 4.0 or earlier versions introduces a runtime dependency on the .NET Framework 4.5 or a later version.
@@ -34,8 +34,6 @@ The change in signing the manifest with SHA-256 even when an app targets the .NE
### Category
ClickOnce
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#ClickOnce)
<!--
### Notes
Only affects WinServer 2003; there is a KB to address it. Could flag it if we detect click-once being used (especially if it has a SHA-1 code-signing cert)

2
Documentation/compatibility/assemblies-compiled-with-regex_compiletoassembly-breaks-between-4_0-and-4_5.md
View File

@@ -29,6 +29,4 @@ To work around this problem, you can do either of the following:
### Category
Core
[More information](https://msdn.microsoft.com/en-us/library/hh367887\(v=vs.110\).aspx#core)
<!-- breaking change id: 74 -->

2
Documentation/compatibility/blockingcollection_trytakefromany-does-not-throw-anymore.md
View File

@@ -35,6 +35,4 @@ If TryTakeFromAny returning -1 or TakeFromAny throwing were used for control-flo
### Category
Core
[More information](https://msdn.microsoft.com/en-us/library/hh367887#core)
<!-- breaking change id: 18 -->

2
Documentation/compatibility/calling-createdefaultauthorizationcontext-with-a-null-argument-has-changed.md
View File

@@ -31,6 +31,4 @@ In rare cases, WCF apps that use custom authentication may see behavioral differ
### Category
Windows Communication Foundation (WCF)
[More information](https://msdn.microsoft.com/en-us/library/dn833123%28v=vs.110%29.aspx#WCF)
<!-- breaking change id: 138 -->

2
Documentation/compatibility/change-in-behavior-for-task_waitall-methods-with-time-out-arguments.md
View File

@@ -38,6 +38,4 @@ If an <xref:System.AggregateException?displayProperty=name> was being caught as
### Category
Core
[More information](https://msdn.microsoft.com/en-us/library/hh367887\(v=vs.110\).aspx#core)
<!-- breaking change id: 26 -->

2
Documentation/compatibility/change-in-behavior-in-data-definition-language-(ddl)-apis.md
View File

@@ -30,6 +30,4 @@ These changes make it easier to build tools and applications that use the DDL AP
### Category
Entity Framework
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#sql)
<!-- breaking change id: 27 -->

2
Documentation/compatibility/clickonce-supports-sha-256-on-4_0-targeted-apps.md
View File

@@ -27,8 +27,6 @@ to sign ClickOnce apps that target .NET Framework 4 and earlier versions.
### Category
ClickOnce
[More information](https://msdn.microsoft.com/en-us/library/dn833125(v=vs.110).aspx#ClickOnce)
<!--
### Notes
We could possibly detect this by analyzing ClickOnce manifests and looking for SHA-256 certs.

2
Documentation/compatibility/compiler-support-for-type-forwarding-when-multi-targeting-mscorlib.md
View File

@@ -28,6 +28,4 @@ mixed in a single location.
### Category
Core
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#core)
<!-- breaking change id: 56 -->

2
Documentation/compatibility/connection-pool-blocking-period-for-azure-sql-databases-is-removed.md
View File

@@ -24,7 +24,7 @@ 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. For more information, see
[SQL Server Connection Pooling (ADO.NET)](https://msdn.microsoft.com/en-us/library/8xx3tyca(v=vs.110).aspx).
[SQL Server Connection Pooling (ADO.NET)](https://docs.microsoft.com/en-us/dotnet/articles/framework/data/adonet/sql-server-connection-pooling).
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

2
Documentation/compatibility/contentdisposition-datetimes-returns-slightly-different-string.md
View File

@@ -41,6 +41,4 @@ comparison.
### Category
Networking
[More information](https://msdn.microsoft.com/en-us/library/dn833125(v=vs.110).aspx#Networking)
<!-- breaking change id: 78 -->

2
Documentation/compatibility/currentculture-flows-across-tasks.md
View File

@@ -59,6 +59,6 @@ would be preserved across Dispatcher operations.
### Category
Core
[More information](https://msdn.microsoft.com/en-us/library/system.globalization.cultureinfo%28v=vs.110%29.aspx#Async)
[More information](https://docs.microsoft.com/en-us/dotnet/api/system.globalization.cultureinfo#Async)
<!-- breaking change id: 146 -->

2
Documentation/compatibility/dataobject_getdata-now-retrieves-data-as-utf-8.md
View File

@@ -42,8 +42,6 @@ If the old behavior is needed for some reason, the app can target the .NET Frame
### Category
Windows Forms
[More information](https://msdn.microsoft.com/en-us/library/dn720772(v=vs.110).aspx#WinForms)
<!--
### Notes
Don't know what data they're getting. Can give an informational diagnostic if we see the GetData APIs called, though.

2
Documentation/compatibility/dbparameter_precision-and-dbparameter_scale-are-now-public-virtual-members.md
View File

@@ -34,6 +34,4 @@ to work.
### Category
ADO.NET
[More information](https://msdn.microsoft.com/en-us/library/dn458356(v=vs.110).aspx#ADO)
<!-- breaking change id: 68 -->

6
Documentation/compatibility/deserialization-of-objects-across-appdomains-can-fail.md
View File

@@ -10,13 +10,13 @@ Edge
Not planned
### Change Description
In some cases, when an app uses two or more app domains with different application bases, trying to deserialize objects in the logical call context across app domains throws an exception.
In some cases, when an app uses two or more app domains with different application bases, trying to deserialize objects in the logical call context across app domains throws an exception.
- [ ] Quirked
- [ ] Build-time break
### Recommended Action
See [Mitigation: Deserialization of Objects Across App Domains](https://msdn.microsoft.com/en-us/library/dn458353(v=vs.110).aspx)
See [Mitigation: Deserialization of Objects Across App Domains](https://docs.microsoft.com/en-us/dotnet/articles/framework/migration-guide/mitigation-deserialization-of-objects-across-app-domains)
### Affected APIs
* Not detectable via API analysis
@@ -24,6 +24,4 @@ See [Mitigation: Deserialization of Objects Across App Domains](https://msdn.mic
### Category
Core
[More information](https://msdn.microsoft.com/en-us/library/dn458360(v=vs.110).aspx)
<!-- breaking change id: 67 -->

2
Documentation/compatibility/different-exception-handling-for-objectcontext_createdatabase-and-dbproviderservices_createdatabase-methods.md
View File

@@ -34,6 +34,4 @@ SQLExceptions should now also be caught.
### Category
Entity Framework
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#sql)
<!-- breaking change id: 40 -->

2
Documentation/compatibility/ef-no-longer-throws-for-queryviews-with-specific-characteristics.md
View File

@@ -38,6 +38,4 @@ the app's configuration file:
### Category
Entity Framework
[More information](https://msdn.microsoft.com/en-us/library/dn720774(v=vs.110).aspx)
<!-- breaking change id: 69 -->

2
Documentation/compatibility/encoderparameter-ctor-is-obsolete.md
View File

@@ -31,6 +31,4 @@ tools:
### Category
Windows Forms
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#winForms)
<!-- breaking change id: 24 -->

2
Documentation/compatibility/enumerable_empty-always-returns-cached-instance.md
View File

@@ -41,6 +41,4 @@ and expected to sometimes be unequal, explicit empty arrays should be created
### Category
LINQ
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#sql)
<!-- breaking change id: 42 -->

2
Documentation/compatibility/error-codes-for-maxrequestlength-or-maxreceivedmessagesize-are-different.md
View File

@@ -37,6 +37,4 @@ You must modify any code that performs processing based on an HTTP 400 status co
### Category
Windows Communication Foundation (WCF)
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#wcf)
<!-- breaking change id: 45 -->

2
Documentation/compatibility/eventlistener-truncates-strings-with-embedded-nulls.md
View File

@@ -36,6 +36,4 @@ be updated, if possible, to not use embedded null characters.
### Category
Core
[More information](https://msdn.microsoft.com/en-us/library/dn458360%28v=vs.110%29.aspx#Core)
<!-- breaking change id: 46 -->

2
Documentation/compatibility/eventsource_writeevent-impls-must-pass-writeevent-the-same-parameters-that-it-received-(plus-id).md
View File

@@ -33,6 +33,4 @@ process for an event source that violates this contract.
### Category
Core
[More information](https://msdn.microsoft.com/en-us/library/dn458360(v=vs.110).aspx)
<!-- breaking change id: 31 -->

4
Documentation/compatibility/exceptions-during-unobserved-processing-in-system_threading_tasks_task-no-longer-propagate-on-finalizer-thread.md
View File

@@ -29,7 +29,7 @@ finalizer thread, the previous behavior can be restored by providing an
appropriate handler for the
<xref:System.Threading.Tasks.TaskScheduler.UnobservedTaskException>
event, or by setting a
[runtime configuration element](https://msdn.microsoft.com/en- us/library/jj160346%28v=vs.110%29.aspx).
[runtime configuration element](https://docs.microsoft.com/en-us/dotnet/articles/framework/configure-apps/file-schema/runtime/throwunobservedtaskexceptions-element).
### Affected APIs
* `M:System.Threading.Tasks.Task.Run(System.Action)`
@@ -46,6 +46,4 @@ event, or by setting a
### Category
Core
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#core)
<!-- breaking change id: 55 -->

2
Documentation/compatibility/httprequest_contentencoding-property-prohibits-utf7.md
View File

@@ -34,6 +34,4 @@ element.
### Category
ASP.NET
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#asp)
<!-- breaking change id: 43 -->

2
Documentation/compatibility/httputility_javascriptstringencode-escapes-ampersand.md
View File

@@ -31,6 +31,4 @@ in your configuration file.
### Category
ASP.NET
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#asp)
<!-- breaking change id: 44 -->

2
Documentation/compatibility/iasyncresult_completedsynchronously-property-must-be-correct-for-the-resulting-task-to-complete.md
View File

@@ -57,6 +57,4 @@ completed synchronously or not.
### Category
Core
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#core)
<!-- breaking change id: 58 -->

2
Documentation/compatibility/il-ret-not-allowed-in-a-try-region.md
View File

@@ -24,8 +24,6 @@ If an app is generating IL that includes a ret opcode in a try region, the app m
### Category
JIT
[More information](https://msdn.microsoft.com/en-us/library/dn833125(v=vs.110).aspx#RyuJIT)
<!--
### Notes
We could maybe detect this by looking for apps that emit ret opcodes, but we'd have to also know whether they were emitted into a try block.

2
Documentation/compatibility/list_foreach-can-throw-exception-when-modifying-list-item.md
View File

@@ -33,6 +33,4 @@ behavior, though, an app may target .NET 4.0.
### Category
Core
[More information](https://msdn.microsoft.com/en-us/library/hh367887\(v=vs.110\).aspx#core)
<!-- breaking change id: 5 -->

2
Documentation/compatibility/log-file-name-created-by-the-objectcontext_createdatabase-method-has-changed-to-match-sql-server-specifications.md
View File

@@ -33,6 +33,4 @@ expect the standard _log.ldf file name format.
### Category
Entity Framework
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#sql)
<!-- breaking change id: 59 -->

2
Documentation/compatibility/machinekey_encode-and-machinekey_decode-methods-are-now-obsolete.md
View File

@@ -33,6 +33,4 @@ using an older compiler. The APIs are still supported.
### Category
ASP.NET
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#asp)
<!-- breaking change id: 28 -->

4
Documentation/compatibility/managed-browser-hosting-controls-from-the-_net-framework-1_1-and-2_0-are-blocked.md
View File

@@ -10,7 +10,7 @@ Minor
Not planned
### Change Description
Hosting these controls is blocked in Internet Explorer.
Hosting these controls is blocked in Internet Explorer.
- [ ] Quirked
- [ ] Build-time break
@@ -24,6 +24,4 @@ Internet Explorer will fail to launch an application that uses managed browser h
### Category
Web Applications
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#web)
<!-- breaking change id: 64 -->

2
Documentation/compatibility/mef-catalogs-implement-ienumerable-and-therefore-can-no-longer-be-used-to-create-a-serializer.md
View File

@@ -29,6 +29,4 @@ Can no longer use MEF to create a serializer
### Category
Managed Extensibility Framework (MEF)
[More information](https://msdn.microsoft.com/en-us/library/hh367887#MEF)
<!-- breaking change id: 12 -->

1
Documentation/compatibility/minfreememorypercentagetoactiveservice-is-now-respected.md
View File

@@ -32,6 +32,5 @@ successfully started and ran in a constrained memory environment may now fail.
### Category
Windows Communication Foundation (WCF)
[More information](https://msdn.microsoft.com/en-us/library/dn458360(v=vs.110).aspx)
<!-- breaking change id: 32 -->

2
Documentation/compatibility/new-(ambiguous)-dispatcher_invoke-overloads-could-result-in-different-behavior.md
View File

@@ -41,6 +41,4 @@ method overload.
### Category
Windows Workflow Foundation (WF)
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#wwf)
<!-- breaking change id: 23 -->

2
Documentation/compatibility/new-enum-values-in-wpf's-pagerangeselection.md
View File

@@ -35,8 +35,6 @@ should be modified, though.
### Category
Windows Presentation Foundation (WPF)
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#wpf)
<!--
### Notes
Look for cast to PageRangeSelection, or <xref:System.Enum.GetNames(System.Type)> or <xref:System.Enum.GetValues(System.Type)> calls taking this type as input

2
Documentation/compatibility/no-longer-able-to-set-enableviewstatemac-to-false.md
View File

@@ -24,6 +24,4 @@ EnableViewStateMac must be assumed to be true, and any resulting MAC errors must
### Category
ASP.NET
[More information](https://msdn.microsoft.com/en-us/library/dn720774#ASP_NET)
<!-- breaking change id: 14 -->

2
Documentation/compatibility/objectcontext_translate-and-objectcontext_executestorequery-now-support-enum-type.md
View File

@@ -27,6 +27,4 @@ If Translate or ExecuteStoreQuery was called on an enum type in .NET 4.0, '0' wa
### Category
Entity Framework
[More information](https://msdn.microsoft.com/en-us/library/hh367887\(v=vs.110\).aspx#sql)
<!-- breaking change id: 41 -->

2
Documentation/compatibility/obsoleteattribute-exports-as-both-obsoleteattribute-and-deprecatedattribute-in-winmd-scenarios.md
View File

@@ -36,6 +36,4 @@ result in build warnings.
### Category
Core
[More information](https://msdn.microsoft.com/en-us/library/dn458356(v=vs.110).aspx)
<!-- breaking change id: 48 -->

2
Documentation/compatibility/only-tls-1_0-1_1-and-1_2-protocols-supported-in-system_net_servicepointmanager-and-system_net_security_sslstream.md
View File

@@ -39,6 +39,4 @@ this feature in either of two ways:
### Category
Networking
[More information](https://msdn.microsoft.com/en-us/library/dn833123(v=vs.110).aspx#Net)
<!-- breaking change id: 137 -->

6
Documentation/compatibility/opt-in-break-to-revert-from-different-4_5-sql-generation-to-simpler-4_0-sql-generation.md
View File

@@ -10,7 +10,7 @@ Transparent
Not planned
### Change Description
Queries that produce JOIN statements and contain a call to a limiting operation without first using OrderBy now produce simpler SQL. After upgrading to .NET Framework 4.5, these queries produced more complicated SQL than previous versions.
Queries that produce JOIN statements and contain a call to a limiting operation without first using OrderBy now produce simpler SQL. After upgrading to .NET Framework 4.5, these queries produced more complicated SQL than previous versions.
- [ ] Quirked
- [x] Optional
@@ -20,7 +20,7 @@ Queries that produce JOIN statements and contain a call to a limiting operation
This feature is disabled by default. If Entity Framework generates extra JOIN statements that cause performance degradation, you can enable this feature by adding the following entry to the `<appSettings>` section of the application configuration (app.config) file:
```xml
<add key="EntityFramework_SimplifyLimitOperations" value="true" />
<add key="EntityFramework_SimplifyLimitOperations" value="true" />
```
### Affected APIs
@@ -29,8 +29,6 @@ This feature is disabled by default. If Entity Framework generates extra JOIN st
### Category
Entity Framework
[More information](https://msdn.microsoft.com/en-us/library/dn720772(v=vs.110).aspx)
<!-- MSDN lists this as a 'minor'-scope break, but it is 'transparent' here because it is an opt-in break -->
<!-- breaking change id: 50 -->

2
Documentation/compatibility/page_loadcomplete-event-no-longer-causes-system_web_ui_webcontrols_entitydatasource-control-to-invoke-data-binding.md
View File

@@ -38,8 +38,6 @@ earlier in the post-back.
### Category
ASP.NET
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#asp)
<!--
### Notes
This change produces different behavior in the unlikely event that applications rely on invoking data binding in the Page.LoadComplete event.

2
Documentation/compatibility/persian-calendar-now-uses-the-hijri-solar-algorithm.md
View File

@@ -34,6 +34,4 @@ Be aware that some early or late dates may be slightly different when using the
### Category
Core
[More information](https://msdn.microsoft.com/en-us/library/dn833125%28v=vs.110%29.aspx#Core)
<!-- breaking change id: 134 -->

2
Documentation/compatibility/reflection-objects-can-no-longer-be-passed-from-managed-code-to-out-of-process-dcom-clients.md
View File

@@ -34,6 +34,4 @@ Update marshaling code to work with non-reflection objects
### Category
Core
[More information](https://msdn.microsoft.com/en-us/library/dn833125(v=vs.110).aspx#Core)
<!-- breaking change id: 77 -->

6
Documentation/compatibility/resolveassemblyreference-task-now-warns-of-dependencies-with-the-wrong-architecture.md
View File

@@ -10,7 +10,7 @@ Minor
Planned
### Change Description
The task emits a warning, MSB3270, which indicates that a reference or any of its dependencies does not match the app's architecture. For example, this occurs if an app that was compiled with the anycpu option includes an x86 reference. Such a scenario could result in an app failure at run time (in this case, if the app is deployed as an x64 process).
The task emits a warning, MSB3270, which indicates that a reference or any of its dependencies does not match the app's architecture. For example, this occurs if an app that was compiled with the anycpu option includes an x86 reference. Such a scenario could result in an app failure at run time (in this case, if the app is deployed as an x64 process).
- [ ] Quirked
- [x] Build-time break
@@ -18,7 +18,7 @@ The task emits a warning, MSB3270, which indicates that a reference or any of it
### Recommended Action
There are two areas of impact:
* Recompilation generates warnings that did not appear when the app was compiled under a previous version of MSBuild. However, because the warning identifies a possible source of runtime failure, it should be investigated and addressed.
* Recompilation generates warnings that did not appear when the app was compiled under a previous version of MSBuild. However, because the warning identifies a possible source of runtime failure, it should be investigated and addressed.
* If warnings are treated as errors, the app will fail to compile.
### Affected APIs
@@ -27,6 +27,4 @@ There are two areas of impact:
### Category
MSBuild
[More information](https://msdn.microsoft.com/en-us/library/dn458356(v=vs.110).aspx)
<!-- breaking change id: 49 -->

2
Documentation/compatibility/soapformatter-cannot-deserialize-hashtable-and-similar-ordered-collection-objects.md
View File

@@ -40,6 +40,4 @@ to be resilient to .NET Framework changes.
### Category
Serialization
[More information](https://msdn.microsoft.com/en-us/library/hh367887\(v=vs.110\).aspx#core)
<!-- breaking change id: 1 -->

2
Documentation/compatibility/some-workflow-drag-and-drop-apis-are-obsolete.md
View File

@@ -31,6 +31,4 @@ using an older compiler. The APIs are still supported.
### Category
Windows Workflow Foundation (WF)
[More information](https://msdn.microsoft.com/en-us/library/hh367887#wwf)
<!-- breaking change id: 22 -->

6
Documentation/compatibility/sql_variant-data-uses-sql_variant-collation-rather-than-database-collation.md
View File

@@ -10,13 +10,13 @@ Transparent
Not planned
### Change Description
`sql_variant` data uses `sql_variant` collation rather than database collation.
`sql_variant` data uses `sql_variant` collation rather than database collation.
- [ ] Quirked
- [ ] Build-time break
### Recommended Action
This change addresses possible data corruption if the database collation differs from the `sql_variant` collation. Applications that rely on the corrupted data may experience failure.
This change addresses possible data corruption if the database collation differs from the `sql_variant` collation. Applications that rely on the corrupted data may experience failure.
### Affected APIs
* Not detectable via API analysis
@@ -24,6 +24,4 @@ This change addresses possible data corruption if the database collation differs
### Category
Data
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#xml)
<!-- breaking change id: 72 -->

2
Documentation/compatibility/sqlbulkcopy-uses-destination-column-encoding-for-strings.md
View File

@@ -38,6 +38,4 @@ column) or catch <xref:System.Data.SqlClient.SqlException?displayProperty=name>s
### Category
Data
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#xml)
<!-- breaking change id: 71 -->

10
Documentation/compatibility/sqlconnection-can-no-longer-connect-to-sql-server-1997-or-databases-using-the-via-adapter.md
View File

@@ -10,9 +10,9 @@ Edge
Planned
### Change Description
Connections to SQL Server databases using the [Virtual Interface Adapter (VIA) protocol](https://technet.microsoft.com/en-us/library/ms191229%28v=sql.105%29.aspx) are no longer supported.
The protocol used to connect to a SQL Server database is visible in the connection string. A VIA connection will contain via:\<servername\>.
If this app is connecting to SQL via a protocol other than VIA (tcp: or np: for example), then no breaking change will be encountered.
Connections to SQL Server databases using the [Virtual Interface Adapter (VIA) protocol](https://technet.microsoft.com/en-us/library/ms191229%28v=sql.105%29.aspx) are no longer supported.
The protocol used to connect to a SQL Server database is visible in the connection string. A VIA connection will contain via:\<servername\>.
If this app is connecting to SQL via a protocol other than VIA (tcp: or np: for example), then no breaking change will be encountered.
Also, connections to SQL Server 7 (1997) are no longer supported.
@@ -20,7 +20,7 @@ Also, connections to SQL Server 7 (1997) are no longer supported.
- [ ] Build-time break
### Recommended Action
The VIA protocol is deprecated, so an alternative protocol should be used to connect to SQL databases. The most common protocol used is TCP/IP. Instructions for enabling the TCP/IP protocol can be found [here](https://msdn.microsoft.com/en-us/library/bb909712(v=vs.90).aspx). If the database is only accessed from within an intranet, the shared pipes protocol may provide better performance if the network is slow.
The VIA protocol is deprecated, so an alternative protocol should be used to connect to SQL databases. The most common protocol used is TCP/IP. Instructions for enabling the TCP/IP protocol can be found [here](https://msdn.microsoft.com/en-us/library/bb909712(v=vs.120).aspx). If the database is only accessed from within an intranet, the shared pipes protocol may provide better performance if the network is slow.
### Affected APIs
* `M:System.Data.SqlClient.SqlConnection.#ctor(System.String)`
@@ -29,6 +29,4 @@ The VIA protocol is deprecated, so an alternative protocol should be used to con
### Category
Data
[More information](https://msdn.microsoft.com/en-us/library/hh367887%28v=vs.110%29.aspx#sql)
<!-- breaking change id: 70 -->

2
Documentation/compatibility/sslstream-support-for-tls-alerts.md
View File

@@ -18,7 +18,7 @@ be thrown by the first I/O Read/Write operation. The
<xref:System.ComponentModel.Win32Exception.NativeErrorCode?displayProperty=name>
code for the <xref:System.ComponentModel.Win32Exception?displayProperty=name>
can be mapped to the TLS Alert from the remote party using this
[channel documentation](https://msdn.microsoft.com/en-us/library/windows/desktop/dd721886%28v=vs.85%29.aspx).
[Schannel documentation](https://msdn.microsoft.com/en-us/library/windows/desktop/dd721886%28v=vs.85%29.aspx).
For more information, see
[RFC 2246: Section 7.2.2 Error alerts](https://tools.ietf.org/html/rfc2246#section-7.2.2)

2
Documentation/compatibility/system_activities-is-now-aptca.md
View File

@@ -30,6 +30,4 @@ this change should have no real impact.
### Category
Windows Workflow Foundation (WF)
[More information](https://msdn.microsoft.com/en-us/library/hh367887)
<!-- breaking change id: 20 -->

2
Documentation/compatibility/system_net_peertopeer_collaboration-unavailable-on-windows-8.md
View File

@@ -25,6 +25,4 @@ Apps that support Windows 8 or above must be updated to not depend on this names
### Category
Networking
[More information](https://msdn.microsoft.com/en-us/library/hh367887#network)
<!-- breaking change id: 11 -->

2
Documentation/compatibility/system_servicemodel_web_webservicehost-object-no-longer-adds-a-default-endpoint.md
View File

@@ -40,8 +40,6 @@ endpoints should also be added explicitly (using <xref:System.ServiceModel.Servi
### Category
Windows Communication Foundation (WCF)
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#wcf)
<!--
### Notes
If an explicit endpoint is added, then the expected default endpoint will not exist. An analyzer can look for explicit endpoints being added without a corresponding call to add default endpoints. A code fix is possible here, too, by just calling <xref:System.ServiceModel.ServiceHostBase.AddDefaultEndpoints?displayProperty=name>. Note, though, that this is probably just informational since it's often not something that needs fixed.

2
Documentation/compatibility/system_threading_tasks_task-no-longer-throw-objectdisposedexception-after-object-is-disposed.md
View File

@@ -39,6 +39,4 @@ using <xref:System.Threading.Tasks.Task.Status>.
### Category
Core
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#core)
<!-- breaking change id: 39 -->

2
Documentation/compatibility/system_uri-escaping-now-supports-rfc-3986.md
View File

@@ -34,6 +34,4 @@ URI escaping has changed in .NET 4.5 to support
### Category
Core
[More information](https://msdn.microsoft.com/en-us/library/hh367887\(v=vs.110\).aspx#core)
<!-- breaking change id: 10 -->

2
Documentation/compatibility/system_uri-parsing-adheres-to-rfc-3987.md
View File

@@ -46,6 +46,4 @@ properties' page.
### Category
Core
[More information](https://msdn.microsoft.com/en-us/library/hh367887\(v=vs.110\).aspx#core)
<!-- breaking change id: 6 -->

2
Documentation/compatibility/targetframeworkname-for-default-app-domain-no-longer-defaults-to-null-if-not-set.md
View File

@@ -38,6 +38,4 @@ null, it can be explicitly set to that value.
### Category
Core
[More information](https://msdn.microsoft.com/en-us/library/dn833125(v=vs.110).aspx#Core)
<!-- breaking change id: 75 -->

2
Documentation/compatibility/the-_net-framework-4_6-does-not-use-a-4_5_x_x-version-when-registering-itself-in-the-registry.md
View File

@@ -24,6 +24,6 @@ Update apps probing for a .NET Framework 4.5 install by looking for 4.5 registry
### Category
Setup and Deployment
[More information](https://msdn.microsoft.com/en-us/library/mt125490%28v=vs.110%29.aspx)
[More information](https://docs.microsoft.com/en-us/dotnet/articles/framework/migration-guide/mitigation-product-versioning)
<!-- breaking change id: 122 -->

2
Documentation/compatibility/the-replace-method-in-odata-urls-is-disabled-by-default.md
View File

@@ -32,6 +32,4 @@ only be used after careful review.
### Category
Windows Communication Foundation (WCF)
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#wcf)
<!-- breaking change id: 29 -->

4
Documentation/compatibility/wcf-binding-with-the-transportwithmessagecredential-security-mode.md
View File

@@ -23,7 +23,7 @@ Because this is an opt-in feature, it should not affect the behavior of existing
Because this is an opt-in feature, it should not affect the behavior of existing apps. To control whether the new behavior is used or not, use the following configuration setting:
```
<runtime>
<AppContextSwitchOverrides value="Switch.System.ServiceModel.AllowUnsignedToHeader=true" />
<AppContextSwitchOverrides value="Switch.System.ServiceModel.AllowUnsignedToHeader=true" />
</runtime>
```
@@ -36,6 +36,4 @@ Because this is an opt-in feature, it should not affect the behavior of existing
### Category
Windows Communication Foundation (WCF)
[More information](https://msdn.microsoft.com/en-US/library/mt592686%28v=vs.110%29.aspx)
<!-- breaking change id: 142 -->

2
Documentation/compatibility/webutility_htmldecode-no-longer-decodes-invalid-input-sequences.md
View File

@@ -26,8 +26,6 @@ The change in decoder output should matter only if you store binary data instead
### Category
ASP.NET
[More information](https://msdn.microsoft.com/en-us/library/hh367887\(v=vs.110\).aspx#asp)
<!--
### Notes
This only matters if you store binary data instead of UTF-16 data in string. An analyzer may not add much beyond ApiPort, but we could do basic parameter analysis and potentially implement a code fix

2
Documentation/compatibility/webutility_htmlencode-and-webutility_htmldecode-round-trip-bmp-correctly.md
View File

@@ -35,8 +35,6 @@ the targeted version of the .NET Framework.
### Category
ASP.NET
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#asp)
<!--
### Notes
This shouldn't affect anything. An analyzer may not add much beyond ApiPort, but we could do basic parameter analysis and potentially implement a code fix

2
Documentation/compatibility/wf-serializes-expressions_literal-datetimes-differently.md
View File

@@ -40,8 +40,6 @@ not function correctly.
### Category
Windows Workflow Foundation (WF)
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#wwf)
<!--
### Notes
Will need to dig in a bit to figure out exactly what a repro for this looks like. Probably, identifying Literal<DateTime>/Literal<DateTimeOffset> usage will be sufficient to give an informational diagnostic.

2
Documentation/compatibility/winform's-checkforoverflowunderflow-property-is-now-true-for-system_drawing.md
View File

@@ -26,6 +26,4 @@ an <xref:System.OverflowException?displayProperty=name> exception is thrown.
### Category
Windows Forms
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx)
<!-- breaking change id: 53 -->

14
Documentation/compatibility/winrt-stream-adapters-no-long-call-flushasync-automatically-on-close.md
View File

@@ -10,7 +10,7 @@ Transparent
Not planned
### Change Description
In Windows Store apps, Windows Runtime stream adapters no longer call the FlushAsync method from the Dispose method.
In Windows Store apps, Windows Runtime stream adapters no longer call the FlushAsync method from the Dispose method.
- [ ] Quirked
- [ ] Build-time break
@@ -19,11 +19,11 @@ In Windows Store apps, Windows Runtime stream adapters no longer call the FlushA
This change should be transparent. Developers can restore the previous behavior by writing code like this:
```csharp
using (var stream = GetWindowsRuntimeStream() as Stream)
{
// do something
await stream.FlushAsync();
}
using (var stream = GetWindowsRuntimeStream() as Stream)
{
// do something
await stream.FlushAsync();
}
```
### Affected APIs
@@ -32,6 +32,4 @@ using (var stream = GetWindowsRuntimeStream() as Stream)
### Category
Core
[More information](https://msdn.microsoft.com/en-us/library/dn458360(v=vs.110).aspx)
<!-- breaking change id: 47 -->

2
Documentation/compatibility/workflow-3_0-types-are-obsolete.md
View File

@@ -24,6 +24,4 @@ New WWF 4.0 APIs (in System.Activities) should be used instead. An example of us
### Category
Windows Workflow Foundation (WF)
[More information](https://msdn.microsoft.com/en-us/library/hh367887#wwf)
<!-- breaking change id: 21 -->

2
Documentation/compatibility/wpf-datatemplate-elements-are-now-visible-to-uia.md
View File

@@ -36,6 +36,4 @@ counts or indexes for UIA elements may need updated with new values.
### Category
Windows Presentation Foundation (WPF)
[More information](https://msdn.microsoft.com/en-us/library/hh367887\(v=vs.110\).aspx#wpf)
<!-- breaking change id: 3 -->

2
Documentation/compatibility/wpf-dispatchersynchronizationcontext_createcopy-now-returns-a-new-copy-instead-of-the-current-instance.md
View File

@@ -42,6 +42,4 @@ affected code paths should be enough to determine if this poses any problem.
### Category
Windows Presentation Foundation (WPF)
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#wpf)
<!-- breaking change id: 38 -->

14
Documentation/compatibility/wpf-layout-rounding-of-margins-has-changed.md
View File

@@ -1,4 +1,4 @@
## WPF layout rounding of margins has changed
## WPF layout rounding of margins has changed
### Scope
Minor
@@ -10,13 +10,13 @@ Minor
Not planned
### Change Description
The way in which margins are rounded and borders and the background inside of them has changed. As a result of this change:
The way in which margins are rounded and borders and the background inside of them has changed. As a result of this change:
- The width or height of elements may grow or shrink by at most one pixel.
- The placement of an object can move by at most one pixel.
- Centered elements can be vertically or horizontally off center by at most one pixel.
- The width or height of elements may grow or shrink by at most one pixel.
- The placement of an object can move by at most one pixel.
- Centered elements can be vertically or horizontally off center by at most one pixel.
By default, this new layout is enabled only for apps that target the .NET Framework 4.6.
By default, this new layout is enabled only for apps that target the .NET Framework 4.6.
- [x] Quirked
- [ ] Build-time break
@@ -32,6 +32,6 @@ Apps that target the .NET Framework 4.6 but want WPF controls to render using th
### Category
Windows Presentation Foundation (WPF)
[More information](https://msdn.microsoft.com/en-us/library/mt298997(v=vs.110).aspx)
[More information](https://docs.microsoft.com/en-us/dotnet/articles/framework/migration-guide/mitigation-wpf-layout)
<!-- breaking change id: 139 -->

6
Documentation/compatibility/wpf-spell-checking-in-text-enabled-controls-will-not-work-in-windows-10-for-languages-not-in-the-input-language-list.md
View File

@@ -10,9 +10,9 @@ Edge
Not planned
### Change Description
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.
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.
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.
- [ ] Quirked
- [ ] Build-time break
@@ -26,6 +26,4 @@ Be aware that the language or text to be spell-checked must be added as an input
### Category
Windows Presentation Foundation (WPF)
[More information](https://msdn.microsoft.com/en-us/library/dn833125(v=vs.110).aspx#WPF)
<!-- breaking change id: 136 -->

2
Documentation/compatibility/wpf-textbox-defaults-to-undo-limit-of-100.md
View File

@@ -24,6 +24,4 @@ If an undo limit of 100 is too low, the limit can be set explicitly with <xref:S
### Category
Windows Presentation Foundation (WPF)
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx)
<!-- breaking change id: 51 -->

2
Documentation/compatibility/wpf-textbox-selected-text-appears-a-different-color-when-the-text-box-is-inactive.md
View File

@@ -30,6 +30,4 @@ property to `false`.
### Category
Windows Presentation Foundation (WPF)
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#wpf)
<!-- breaking change id: 4 -->

2
Documentation/compatibility/wpf-textbox_text-can-be-out-of-sync-with-databinding.md
View File

@@ -32,6 +32,4 @@ property to `false`.
### Category
Windows Presentation Foundation (WPF)
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#wpf)
<!-- breaking change id: 52 -->

2
Documentation/compatibility/wpf-windows-are-rendered-without-clipping-when-extending-outside-a-single-monitor.md
View File

@@ -24,6 +24,4 @@ This behavior (whether to clip or not) can be explicitly set using the `<EnableM
### Category
Windows Presentation Foundation (WPF)
[More information](https://msdn.microsoft.com/en-us/library/dn833125(v=vs.110).aspx#WPF)
<!-- breaking change id: 135 -->

2
Documentation/compatibility/x509certificate2_tostring(bool)-does-not-throw-now-when-_net-cannot-handle-the-certificate.md
View File

@@ -33,6 +33,4 @@ in which the API would have previously thrown.
### Category
Core
[More information](https://msdn.microsoft.com/en-us/library/dn833125\(v=vs.110\).aspx#Core)
<!-- breaking change id: 76 -->

2
Documentation/compatibility/x509certificateclaimset_findclaims-considers-all-claimtypes.md
View File

@@ -36,6 +36,4 @@ compatibility switch.
### Category
Windows Communication Foundation (WCF)
[More information](https://msdn.microsoft.com/en-us/library/mt620031%28v=vs.110%29.aspx#WCF)
<!-- breaking change id: 143 -->

2
Documentation/compatibility/xml-schema-validation-is-stricter.md
View File

@@ -24,6 +24,4 @@ If looser .NET Framework 4.0 validation is needed, the validating application ca
### Category
XML, XSLT
[More information](https://msdn.microsoft.com/en-us/library/hh367887\(v=vs.110\).aspx)
<!-- breaking change id: 2 -->

2
Documentation/compatibility/xmlschemaexception-now-sets-line-positions-properly.md
View File

@@ -34,6 +34,4 @@ properly when SetLineInfo is used while loading XML.
### Category
XML, XSLT
[More information](https://msdn.microsoft.com/en-us/library/hh367887#xml)
<!-- breaking change id: 19 -->

2
Documentation/compatibility/xmltextreader-dtd-entity-expansion-is-limited-to-10000000-characters.md
View File

@@ -46,6 +46,4 @@ value can be passed to `XmlReader.Create` that takes
### Category
XML, XSLT
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx)
<!-- breaking change id: 33 -->

2
Documentation/compatibility/xmlwriter-throws-on-invalid-surrogate-pairs.md
View File

@@ -54,8 +54,6 @@ xml prior to writing them.
### Category
XML, XSLT
[More information](https://msdn.microsoft.com/en-us/library/dn833123\(v=vs.110\).aspx)
<!--
### Notes
Analyzer wouldn't add much over ApiPort, but we could do basic parameter analysis

2
Documentation/compatibility/xslt-forward-compat-now-works.md
View File

@@ -29,6 +29,4 @@ Most apps should be unaffected, however data will be sorted differently in some
### Category
XML, XSLT
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#xml)
<!-- breaking change id: 34 -->

2
Documentation/compatibility/xslt-style-sheet-exception-message-changed.md
View File

@@ -40,6 +40,4 @@ which has not changed.
### Category
XML, XSLT
[More information](https://msdn.microsoft.com/en-us/library/hh367887(v=vs.110).aspx#xml)
<!-- breaking change id: 35 -->