Skip to content

Commit 1085350

Browse files
Jay-o-Waymairaw
Jay-o-Way
and
mairaw
authored
Polish release notes 1.x (dotnet#8357)
* release notes 1.x * escape Co-authored-by: Maira Wenzel <mairaw@microsoft.com> * undo Co-authored-by: Maira Wenzel <mairaw@microsoft.com> * extras * revert titles Co-Authored-By: Maira Wenzel <mairaw@microsoft.com> --------- Co-authored-by: Maira Wenzel <mairaw@microsoft.com>
1 parent f385a9d commit 1085350

35 files changed

+980
-982
lines changed

‎release-notes/1.0/1.0-supported-os.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -21,18 +21,18 @@ See the [Windows Lifecycle Fact Sheet](https://support.microsoft.com/help/13853/
2121

2222
OS | Version | Architectures| Notes
2323
------------------------------|--------------------------------|--------------|-----
24-
Mac OS X | 10.11, 10.12* | x64 | [Apple Support Sitemap](https://support.apple.com/sitemap) <br> [Apple Security Updates](https://support.apple.com/HT201222)
24+
Mac OS X | 10.11, 10.12* | x64 | [Apple Support Sitemap](https://support.apple.com/sitemap) <br/> [Apple Security Updates](https://support.apple.com/HT201222)
2525

2626
\* Supported by latest patch release of .NET Core 1.0
2727

2828
## Linux
2929

3030
OS | Version | Architectures| Notes
3131
------------------------------|--------------------------------|--------------|-----
32-
Red Hat Enterprise Linux <br> CentOS <br> Oracle Linux | 7 | x64 | [Red Hat support policy](https://access.redhat.com/support/policy/updates/errata/) <br> [CentOS lifecycle](https://wiki.centos.org/FAQ/General#head-fe8a0be91ee3e7dea812e8694491e1dde5b75e6d) <br> [Oracle Linux lifecycle](https://www.oracle.com/a/ocom/docs/elsp-lifetime-069338.pdf)
32+
Red Hat Enterprise Linux <br/> CentOS <br/> Oracle Linux | 7 | x64 | [Red Hat support policy](https://access.redhat.com/support/policy/updates/errata/) <br/> [CentOS lifecycle](https://wiki.centos.org/FAQ/General#head-fe8a0be91ee3e7dea812e8694491e1dde5b75e6d) <br/> [Oracle Linux lifecycle](https://www.oracle.com/a/ocom/docs/elsp-lifetime-069338.pdf)
3333
Fedora | 27, 28 (1.1) | x64 | [Fedora lifecycle](https://fedoraproject.org/wiki/End_of_life)
3434
Debian | 8.2+ | x64 | [Debian lifecycle](https://wiki.debian.org/DebianReleases)
35-
Ubuntu <br> Linux Mint | 16.04, 18.04 (1.1) <br> 17 | x64 | [Ubuntu lifecycle](https://wiki.ubuntu.com/Releases) <br> [Linux Mint end of life announcements](https://forums.linuxmint.com/search.php?keywords=%22end+of+life%22&terms=all&author=&sc=1&sf=titleonly&sr=posts&sk=t&sd=d&st=0&ch=300&t=0&submit=Search)
35+
Ubuntu <br/> Linux Mint | 16.04, 18.04 (1.1) <br/> 17 | x64 | [Ubuntu lifecycle](https://wiki.ubuntu.com/Releases) <br/> [Linux Mint end of life announcements](https://forums.linuxmint.com/search.php?keywords=%22end+of+life%22&terms=all&author=&sc=1&sf=titleonly&sr=posts&sk=t&sd=d&st=0&ch=300&t=0&submit=Search)
3636
openSUSE | 42.3+ (1.1) | x64 | [OpenSUSE lifecycle](https://en.opensuse.org/Lifetime)
3737

3838
* \* Supported by the latest patch release of .NET Core 1.1

‎release-notes/1.0/1.0.0-api.md

-1
Original file line numberDiff line numberDiff line change
@@ -106,4 +106,3 @@ additions and a '-' indicates removal.
106106
* [System.Xml.Schema](1.0.0-api/1.0.0-api_System.Xml.Schema.md)
107107
* [System.Xml.Serialization](1.0.0-api/1.0.0-api_System.Xml.Serialization.md)
108108
* [System.Xml.XPath](1.0.0-api/1.0.0-api_System.Xml.XPath.md)
109-

‎release-notes/1.0/1.0.0-contributor-list.md

+829-830
Large diffs are not rendered by default.

‎release-notes/1.0/1.0.0-known-issues.md

+36-29
Original file line numberDiff line numberDiff line change
@@ -9,10 +9,12 @@ See the [.NET Core prequisites document](https://github.com/dotnet/core/blob/mai
99
## NegotiateStream's functionality relies on gssapi implementation
1010

1111
```NegotiateStream``` relies on the gssapi implementation available on the platform:
12+
1213
* On Linux, the default gssapi implementation typically provided is [MIT's krb5 library](https://web.mit.edu/kerberos/), which is available on all the linux platforms.
1314
* On OS X, the default implementation is the heimdal-based GSS.framework.
1415

1516
On both Linux and OS X, NegotiateStream uses SPNEGO and relies on the underlying implementation for supporting Kerberos and NTLM as the underlying security protocol:
17+
1618
* On OS X, GSS.framework supports the SPNEGO mechanism with Kerberos and NTLM as the available security protocols.
1719
* On Linux, the MIT krb5 library supports SPENGO mechanism and Kerberos as the available security protocol. The implementation can also be made to support NTLM by installing the [GSS-NTLMSSP plugin](https://fedorahosted.org/gss-ntlmssp/) or another plugin with similar functionality. The fallback to NTLM is thus dependent on runtime availability of such a plugin. On RHEL and CentOS, the GSS-NTLMSSP plugin is available from the package managers. The same is also available on Ubuntu 16. It may be available for installable on other distributions and versions of Linux. There's no compile time dependency on this plugin.
1820

@@ -21,24 +23,27 @@ On both Linux and OS X, NegotiateStream uses SPNEGO and relies on the underlying
2123
There are some combinations of Kerberos/NTLM and SignOnly/EncryptAndSign/etc. that cause the native ```gss_wrap``` call used by ```NegotiateStream``` on a Unix client to fail when connected to a ```NegotiateStream``` on a Windows server. Here are the failing combinations of credentials and protection level passed in to ```AuthenticateAsClientAsync```:
2224

2325
On Linux:
24-
- Kerberos creds with Sign: Server complains that signature is valid but that the contents are not encrypted.
25-
- NTLM creds with EncrypAndSign: Server rejects signature.
26-
- NTLM creds with Sign: Server rejects signature.
26+
27+
* Kerberos creds with Sign: Server complains that signature is valid but that the contents are not encrypted.
28+
* NTLM creds with EncrypAndSign: Server rejects signature.
29+
* NTLM creds with Sign: Server rejects signature.
2730

2831
On OS X:
29-
- Kerberos creds with Sign: Server complains that signature is valid but the contents are not encrypted.
30-
- NTLM creds with EncryptAndSign: Server complains about message format.
31-
- NTLM creds with Sign: gss_wrap fails on client side.
32+
33+
* Kerberos creds with Sign: Server complains that signature is valid but the contents are not encrypted.
34+
* NTLM creds with EncryptAndSign: Server complains about message format.
35+
* NTLM creds with Sign: gss_wrap fails on client side.
3236

3337
A fix for this issue has been pushed to MIT Kerberos source <https://github.com/krb5/krb5/pull/436>, which will make the fix available for all Unix platforms, starting with krb5-1.15. Red Hat reports the fix will be backported to RHEL 7.
3438

35-
- https://github.com/dotnet/corefx/issues/6767
39+
* <https://github.com/dotnet/corefx/issues/6767>
3640

3741
### Socket.Connect and ConnectAsync instance methods support only one IPAddress
3842

3943
The Socket class provides instance and extension Connect and ConnectAsync methods, each with multiple overloads. Some of these overloads take an IPAddress, some take an array of IPAddresses, some take a string host name, and others take an EndPoint. On Linux and on OS X, only some of these methods are functional in this release, due to the capabilities of the underlying platform. Specifically, any of these overloads that may need to work with multiple addresses will throw a PlatformNotSupportedException; that includes not only the overloads that take an array of IPAddress instances, but also the overloads that take a string host, as well as the overloads that take an EndPoint if a DnsEndPoint is supplied (when the DNS lookup is performed, the host name may end up mapping to multiple addresses).
4044

4145
As a workaround, a new Socket instance may be created for each address to be tried, e.g.
46+
4247
```C#
4348
public static class SocketUtilities
4449
{
@@ -72,13 +77,13 @@ public static class SocketUtilities
7277
}
7378
```
7479

75-
- https://github.com/dotnet/corefx/issues/9235
80+
* <https://github.com/dotnet/corefx/issues/9235>
7681

7782
## HttpClient handler header parsing strictness on Linux and OS X
7883

7984
HttpClient response header parsing logic on Linux and on OS X fairly strictly follows the RFC. Certain "invalid" headers, such as with spaces between the header name and the colon, might be accepted by other browsers or even by HttpClient on Windows, but could be rejected when run on Linux or on OS X.
8085

81-
- https://github.com/dotnet/corefx/issues/9240
86+
* <https://github.com/dotnet/corefx/issues/9240>
8287

8388
## X509 certificate stores not supported on NTFS and FAT volumes on Unix
8489

@@ -105,8 +110,7 @@ When this dependency is not met, an application making direct or indirect use of
105110

106111
Since .NET Core loads libcrypto and libssl via rpath probing, these libraries can be copied into the working directory of an application before being copied to another machine. But when trying to use this configuration, users should be advised that the Homebrew version of libssl has an absolute path dependency on libcrypto. The local copy of libssl may need to be modified to search for libcrypto via rpath with the `install_name_tool` utility.
107112

108-
- https://github.com/dotnet/corefx/issues/9171
109-
113+
* <https://github.com/dotnet/corefx/issues/9171>
110114

111115
## Debian users may experience unexpected failure when using SSL/TLS
112116

@@ -116,13 +120,13 @@ Metadata from the server can cause OpenSSL 1.0.1 to consider the cross-certified
116120

117121
Microsoft has no specific guidance to offer users affected by this configuration state. This is currently tracked as [bug 812488 in the Debian bug system](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812488).
118122

119-
- https://github.com/dotnet/corefx/issues/9244
123+
* <https://github.com/dotnet/corefx/issues/9244>
120124

121125
## HttpClient.GetAsync may fail while handling multiple "WWW-Authenticate: Basic" headers
122126

123127
HttpClient.GetAsync on Windows is unable to process and throws an exception if a server response includes more than one "WWW-Authenticate: Basic" header with different realms.
124128

125-
- https://github.com/dotnet/corefx/issues/9124
129+
* <https://github.com/dotnet/corefx/issues/9124>
126130

127131
## Universal C Runtime dependency on Windows
128132

@@ -132,14 +136,14 @@ If the dependency is not present, applications will fail to run and errors will
132136
```The program can't start because api-ms-win-crt-runtime-1-1-0.dll is missing from your computer. Try reinstalling the program to fix this problem.```
133137
The UCRT dependency can be installed via Windows Update (name: "Update for Universal C Runtime in Windows", per <https://support.microsoft.com/kb/2999226>) and, as a recommended update, it will be installed automatically if the user uses the default settings for Windows Update. It can also be downloaded from [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=48234).
134138

135-
- https://github.com/dotnet/corefx/issues/9083
136-
- https://github.com/dotnet/corefx/issues/9389
139+
* <https://github.com/dotnet/corefx/issues/9083>
140+
* <https://github.com/dotnet/corefx/issues/9389>
137141

138142
## Exceptions due to user limits on OS X
139143

140144
When an app exceeds a user limit (ulimit) on OS X and an exception is thrown, the exception may be for an "internal error" (0x8007054F) rather than representing the actual error that occured. The workaround is to manually increase the ulimit.
141145

142-
- https://github.com/dotnet/coreclr/issues/5782
146+
* <https://github.com/dotnet/coreclr/issues/5782>
143147

144148
## Unexpected OutOfMemoryExceptions on Unix
145149

@@ -152,23 +156,26 @@ If an application experiences this problem and/or is expected to create a large
152156
If an app has a static assembly reference to an assembly that is missing (this is not common), or if an app attempts to use Assembly.Load with an assembly that is missing and is using a handler for the Resolving event to load assemblies from custom locations, the Resolving event may return an invalid reference, which could result in a crash.
153157

154158
The workaround to address the above problem is one of the following:
155-
- Load the assembly using `LoadFromAssemblyName` instead of Assembly.Load.
156-
- Create a custom `AssemblyLoadContext` and override its Load method to resolve the assembly.
157159

158-
- https://github.com/dotnet/coreclr/issues/5837#issuecomment-226657996
160+
* Load the assembly using `LoadFromAssemblyName` instead of Assembly.Load.
161+
* Create a custom `AssemblyLoadContext` and override its Load method to resolve the assembly.
162+
163+
* <https://github.com/dotnet/coreclr/issues/5837#issuecomment-226657996>
159164

160165
## global.json needs to be in UTF-8
161166

162167
If global.json file has an UTF-16 BOM, dotnet commands will fail (due to not supporting a UTF-16 BOM) with the error:
168+
163169
```
164170
A JSON parsing exception occurred: * Line 1, Column 2 Syntax error: Malformed token
165171
```
172+
166173
This situation may arise when using tools that by default produce UTF-16 files with the BOM, such as PowerShell's Out-File cmdlet.
167174

168175
A workaround is to either remove the BOM or change the file's encoding. Visual Studio by default uses UTF-8. If you are using PowerShell, you can specify the encoding for the Out-File cmdlet with the -Encoding argument, `Out-File -Encoding utf8`.
169176

170-
- https://github.com/dotnet/core-setup/issues/185
171-
- https://github.com/dotnet/cli/issues/2159
177+
* <https://github.com/dotnet/core-setup/issues/185>
178+
* <https://github.com/dotnet/cli/issues/2159>
172179

173180
## dotnet restore can fail on Fedora 23 with NSS 3.24 installed with timeouts and SSL connection errors
174181

@@ -178,8 +185,7 @@ At this time, the workaround is to downgrade NSS.
178185
sudo dnf downgrade nspr nss-util nss-softokn-freebl nss-softokn nss-sysinit nss nss-tools
179186
```
180187

181-
- https://github.com/dotnet/cli/issues/3676
182-
188+
* <https://github.com/dotnet/cli/issues/3676>
183189

184190
## Line numbers missing from exception call stack on Windows 7
185191

@@ -197,11 +203,12 @@ catch (Exception ex)
197203
}
198204
```
199205

200-
- https://github.com/dotnet/coreclr/issues/5828
206+
* <https://github.com/dotnet/coreclr/issues/5828>
201207

202208
## Nano Server TP5
203209

204210
When working on TP5 of Nano server, users will encounter the following error if they try to run either portable or self-contained application:
211+
205212
```
206213
Failed to load the dll from [C:\hwapp_s\bin\Debug\netcoreapp1.0\win10-x64\hostpolicy.dll], HRESULT: 0x8007007E
207214
An error occurred while loading required library hostpolicy.dll from [C:\hwapp_s\bin\Debug\netcoreapp1.0\win10-x64]
@@ -224,14 +231,14 @@ Some libraries that P/Invoke into api-set's and target .NET Framework in our nug
224231
Some of the api-sets are installed by the UCRT update: <https://support.microsoft.com/kb/2999226>
225232
and <https://support.microsoft.com/kb/2790113> but these installations may not be a comprehensive fix.
226233

227-
- If you're using project.json you can just reference the Microsoft.NETCore.Windows.ApiSets package from your app and be sure to deploy for runtime win7-x86 or win7-x64, as appropriate.
234+
* If you're using project.json you can just reference the Microsoft.NETCore.Windows.ApiSets package from your app and be sure to deploy for runtime win7-x86 or win7-x64, as appropriate.
228235

229-
- If you're using packages.config you'll need to manually download and extract the packages, as appropriate for the bitness of your app:
230-
- [runtime.win7-x64.Microsoft.NETCore.Windows.ApiSets](https://dotnet.myget.org/F/dotnet-core/api/v2/package/runtime.win7-x64.Microsoft.NETCore.Windows.ApiSets/1.0.1)
231-
- [runtime.win7-x86.Microsoft.NETCore.Windows.ApiSets](https://dotnet.myget.org/F/dotnet-core/api/v2/package/runtime.win7-x86.Microsoft.NETCore.Windows.ApiSets/1.0.1)
236+
* If you're using packages.config you'll need to manually download and extract the packages, as appropriate for the bitness of your app:
237+
* [runtime.win7-x64.Microsoft.NETCore.Windows.ApiSets](https://dotnet.myget.org/F/dotnet-core/api/v2/package/runtime.win7-x64.Microsoft.NETCore.Windows.ApiSets/1.0.1)
238+
* [runtime.win7-x86.Microsoft.NETCore.Windows.ApiSets](https://dotnet.myget.org/F/dotnet-core/api/v2/package/runtime.win7-x86.Microsoft.NETCore.Windows.ApiSets/1.0.1)
232239

233240
## Bash on Ubuntu on Windows
234241

235242
[Bash on Windows (WSL)](https://learn.microsoft.com/windows/wsl/about) is not yet supported by .NET Core. Attempting to run applications in the environment can experience intermittent crashes.
236243

237-
- https://github.com/Microsoft/BashOnWindows/issues/520
244+
* <https://github.com/Microsoft/BashOnWindows/issues/520>

‎release-notes/1.0/1.0.0-manifest.md

-1
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,6 @@ To see release details for each major component of .NET Core, visit the [Core](h
6464
| Microsoft.NETCore.Targets | 1.0.1 |
6565
| Microsoft.NETCore.Windows.ApiSets | 1.0.1 |
6666

67-
6867
## Microsoft.NETCore.App (1.0.0)
6968

7069
| NuGet Package | Package Version |

‎release-notes/1.0/1.0.0.md

+6-6
Original file line numberDiff line numberDiff line change
@@ -43,8 +43,8 @@ No changes from RC2.
4343

4444
### Introduction of .NET Core API Documentation
4545

46-
* Conceptual: https://learn.microsoft.com/dotnet/articles/core/index
47-
* API: https://learn.microsoft.com/dotnet/core/api/index
46+
* Conceptual: <https://learn.microsoft.com/dotnet/articles/core/index>
47+
* API: <https://learn.microsoft.com/dotnet/core/api/index>
4848

4949
### Production-quality .NET Core Runtime and Framework libraries
5050

@@ -69,13 +69,13 @@ New .NET Core APIs
6969
* System.Net.Http - new properties on HttpClientHandler
7070
* System.Net.Sockets - add back Tcp|UdpClient.Client property
7171
* System.Reflection.Metadata - MetadataReaderProvider
72-
* Many types have been removed from the 1.3 surface area and moved to 1.4 which remains in pre-release. If you depend on these types update to the 1.4.0 pre-release package.
72+
* Many types have been removed from the 1.3 surface area and moved to 1.4 which remains in pre-release. If you depend on these types update to the 1.4.0 pre-release package.
7373
* System.Resources.ReaderWriter - types are now in separate assemblies System.Resources.Reader and System.Resources.Writer
7474
* System.Runtime.CompilerServices.Unsafe - New static helper methods for dealing with unsafe pointers
7575
* System.Security.Cryptography
76-
* ECDsa supports creating keys for arbitrary named and explicit curves (Windows 10, OS X, Linux)
77-
* ECDsa supports importing and exporting keys via the platform-independent ECParameters type
78-
* EnvelopedCms is now supported via the System.Security.Cryptography.Pkcs package
76+
* ECDsa supports creating keys for arbitrary named and explicit curves (Windows 10, OS X, Linux)
77+
* ECDsa supports importing and exporting keys via the platform-independent ECParameters type
78+
* EnvelopedCms is now supported via the System.Security.Cryptography.Pkcs package
7979
* System.Security.SecureString
8080
* System.Text.RegularExpressions - precompiled regex
8181

‎release-notes/1.0/1.0.1-known-issues.md

-4
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,6 @@ This document lists known issues for *.NET Core 1.0.1* and *.NET Core SDK 1.0.0
66

77
`dotnet` command not found after installing on a clean macOS Sierra system that previously did not have .NET Core SDK installed.
88

9-
109
`ln -s /usr/local/share/dotnet/dotnet /usr/local/bin` will create the symbolic link in the correct location and `dotnet` should now work.
1110

1211
## .NET Core 1.0.1 - VS 2015 Tooling Preview 2 installer fails
@@ -19,6 +18,3 @@ First, install appropriate VC_Redist:
1918
- [vc_redist.x64.exe](https://go.microsoft.com/fwlink/?LinkId=615460)
2019

2120
Then install [.NET Core 1.0.1 - VS 2015 Tooling Preview 2](https://go.microsoft.com/fwlink/?LinkID=827524)
22-
23-
24-

‎release-notes/1.0/1.0.1-manifest.md

-1
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,6 @@ Updated packages at the top of the table and marked with an *.
7777
| Microsoft.NETCore.Targets | 1.0.1 |
7878
| Microsoft.NETCore.Windows.ApiSets | 1.0.1 |
7979

80-
8180
## Microsoft.NETCore.App (1.0.1)
8281

8382
Updated packages at the top of the table and marked with an *.

‎release-notes/1.0/1.0.1-sdk-release-notes.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -54,4 +54,4 @@ You can also use the .NET For runtime images, which contain the latest runtime u
5454
Symbol packages for .NET 1.0.4 are available for download from the following locations.
5555

5656
* [CoreCLR](https://go.microsoft.com/fwlink/?LinkID=843411)
57-
* [CoreFX](https://go.microsoft.com/fwlink/?LinkID=843414)
57+
* [CoreFX](https://go.microsoft.com/fwlink/?LinkID=843414)

‎release-notes/1.0/1.0.10.md

+1-2
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ The [.NET Core Docker images](https://hub.docker.com/r/microsoft/dotnet/) have b
1919

2020
## Azure AppServices
2121

22-
Deployment of this update to Azure AppServices is in process. Because AppServices is a high availability service, the deployment is carfully staged across regions over a period of time. Deployment will begin in the West US 2 and North Central US regions with remaining regions following over a few days.
22+
Deployment of this update to Azure AppServices is in process. Because AppServices is a high availability service, the deployment is carefully staged across regions over a period of time. Deployment will begin in the West US 2 and North Central US regions with remaining regions following over a few days.
2323

2424
## Known Issues
2525

@@ -55,4 +55,3 @@ Microsoft is aware of a security vulnerability in the public versions of .NET Co
5555
#### CoreFX
5656

5757
#### CoreCLR
58-

0 commit comments

Comments
 (0)