Today, we are releasing a new set of reliability and quality updates for .NET Core 1.0. This month’s update is our second Long Term Support (LTS) update and includes updated versions of multiple packages in .NET Core, ASP.NET Core and Entity Framework Core. We recommend everyone on the 1.0.* LTS track move to this update immediately.
How to Obtain the Updates
- Download and install the .NET Core version 1.0.3 Runtime or SDK
- Update dependencies in your applications to the latest patch version for 1.0
.NET Core 1.0.3 Fixes
For more information on the change, please see the .NET Core 1.0.3 release notes.
Debugging
- Visual Studio Remote Debugger with CoreCLR executables on Nano server does not work. 7316
- Generate symbol packages for CoreCLR binaries. 5832
WinHttpHandler Fixes:
- Nonstandard HTTP authentication responses. 11452, 11456
- Basic authentication with default credentials. 11266
- Uri escaping for HTTP requests. 11156
- WinHttpRequestState objects leak during HTTP resends. 11693
ASP.NET Core Fixes
- Exception page showing only method names in the call stack. 335
- ActionResults returned from controller actions rendered as JSON, instead of executed. 5344
- Html.ValidationSummary helper throwing exception when model binding a collection. 5157
- WebHost.Run() completes before ApplicationStopping. 873
- AntiForgeryValidation attribute conflict with CookieAuthenticationEvents OnRedirectToLogin event handler. 1009
- UvException (Error -4047 EPIPE broken pipe) timing out HTTP requests. 1208, 1207
- UserSecrets causes design-time tools to crash. 543
Entity Framework Core Fixes
- Query: Regression: GroupBy multiple keys throws exception in 1.0.1. 6620
- Select with Ternary Operator/CASE-WHEN Server Side Evaluation. 6598
- Query: Including a collection doesn’t close the connection. 6581
- Query: Take() with Include() generates incorrect SQL. 6530
- Query: Include() for related collections are dropped when use Skip(). 6492
- Query: Port Include() performance improvement to 1.0.2. 6760
- Tools: Better ConfigureDesignTimeServices entry point. 5617
- Query: Entities not being released due to leak in query caching. 6737
F# Changes
- Update to all dotnet new templates ( web/console/lib/xunittest )
- Added dotnet new ASP.NET Core template ( dotnet new -l fsharp -t web )
- Added dotnet new XUnit test library template ( dotnet new -l fsharp -t xunittest )
If you are having trouble, we want to know about it. Please report issues on GitHub issue – 391.
Thanks to everyone who reported issues and contributed!
I’m confused. I’m currently running 1.1.0, am I supposed to move to 1.0.3?
No, it looks like it’s just fixes to the older (long term support) version.
Joe is correct. Since you are using 1.1.0, you are already on the FTS track and you can disregard this update. Sorry for the confusion. I changed the wording a bit to reflect that only those using LTS (1.0) tracks should install this update.
Kendra going forward to Feb. When 1.0.4 supposed to come out, will 1.1.0 have those fixes following up what you said about 1.0.3? I assume you actively have to merge up everything from the minor releases back to 1.1.0, which means we have to actively download 1.1.0. Is that correct?
Yeah this is confusing and what happens with the actual versioning of the libraries, how would we know which version to use?
Sorry it took me longer to get back to you on this one. I had to ask around! Yes, all the fixes we make in the 1.0.* track are also made in the 1.1.* track if they are still applicable. If you are using the 1.1.* track and are hearing about a fix in 1.0.* that is not present in the current 1.1.* track please create an issue and let us know!
Is there going to be an updated package for EF Core on NuGet? The latest version I see is 1.1.0 which has been out for a while.
Yes, but this update is for the LTS track. The EF package is posted for the LTS track here: https://www.nuget.org/packages/Microsoft.EntityFrameworkCore/1.0.2
If you are using 1.1.0 then you are on the FTS track and you do not need to install this update.
It looks like the Windows Server Hosting download link for the LTS Runtime (DotNetCore.1.0.3+1.1.0-WindowsHosting.exe) is broken on https://www.microsoft.com/net/download/core#/lts/runtime
https://go.microsoft.com/fwlink/?linkid=837808
forwards to:
https://download.microsoft.com/download/7/E/4/7E407C90-0154-42BA-8B9E-766C9CB94C3C/DotNetCore.1.0.3+1.1.0-WindowsHosting.exe
which 404s.
Sorry for the late response. We are tracking down the fix for this. Thank you for pointing this out!
It looks like this installer is not working.. Have tested on Windows 7, Server 2016 and 2012r2.
Can you please look into this for us?
[39F0:425C][2016-12-15T15:49:56]e000: Error 0x80070570: Failed to extract all files from container, erf: 1:4:0
[39F0:45BC][2016-12-15T15:49:56]e000: Error 0x80070570: Failed to begin and wait for operation.
[39F0:45BC][2016-12-15T15:49:56]e000: Error 0x80070570: Failed to extract payload: a3 from container: WixAttachedContainer
[39F0:45BC][2016-12-15T15:49:56]e312: Failed to extract payloads from container: WixAttachedContainer to working path: C:\Users\[snip]\AppData\Local\Temp\{C94400E2-CD92-4164-A1C9-FE203730800F}\.cr\DotNetCore.1.0.3_1.1.0-WindowsHosting.exe, error: 0x80070570.
[39F0:1BE8][2016-12-15T15:49:56]e000: Error 0x80070570: Cache thread exited unexpectedly.
Talking to the team now. Thank you for reporting this and including your error message!
I am also facing this exact same error just like @CJ.
Tried installing Windows Server Hosting download link for the LTS Runtime (DotNetCore.1.0.3+1.1.0-WindowsHosting.exe) on Windows 10 and Win2012 Standard. At first the through was, the download is corrupt. But then I download multiple times on different machines and network and see the same error. Also, I tried with launching MSI with ‘Run as administrator’.
The Windows Server Hosting download link for the LTS Runtime is not working currently. Much of the team is on holiday right now, but this will be fixed in the new year. I apologize for the inconvenience! (I tried taking the broken link off the .NET Core download page, but unfortunately the maintainers of that page are also off on holiday.) 🙂
We’ve got the Windows Server Hosting 1.0.3 Runtime download working now if you’d like to try it out.
I tried the new link and the installation works now.
I tried the updated link (as per Kendra’s comment) and the new download install properly without the error. Thank you.
Any news on this? Failing to install on windows 2016 clean install.
I apologize for the failing install on the Windows Server Hosting download link for the LTS Runtime. Much of the team will be back January 3rd and they will look into it then. I’ll definitely comment here once it is working.
We’ve got the Windows Server Hosting 1.0.3 Runtime download working now if you’d like to try it out.
We’ve got the Windows Server Hosting 1.0.3 Runtime download working now if you’d like to try it out. https://www.microsoft.com/net/download/core#/runtime
So F# projects seem to have issues with 1.1.0:
– they end up with references to both 1.0.0 and 1.1.0 in the project.lock.json
– the new F# templates aren’t available in 1.1.0
So I guess I should just downgrade to 1.0.3, but the Linux install instruction seem to only be for 1.1.0. Are there a 1.0.3 Linux installers somewhere?
oh found it: https://www.microsoft.com/net/download/linux
Congratulations! Things weren’t enough complicated… Now you’re introducing branching on releases, wich helps us a lot on configuring everything. That added to the thousand packages with hundred versions, each one versioned different, a miriad of preview releases with incoherent naming, late changes to the apis, continous delays on delivering products, no stable version of Entity Framework Core yet (after more than two years), inability to decide a way to configure a project (we’re looping through cproj and xproj) with json (or not)….
Ayeah! I wonder if anybody there has a clear vision about were all this is going, because it’s long since I’ve lost myself among so transitory decisions. I also wonder if tthere is somebody there at Microsoft perceiving a salary for all this work or you’ve left all responsibility to the community for such a big change. I’m a freelance developer and my life is a hell since I bet for the (very well sold) mega fantastic ultra performant life changing vNext version on it’s latest betas. I feel really fustrated on how this is being managed (whoever) manages this.
So thanks for fixing all this bugs on the LTS branch but, do this bugs exist on the FTS one? What does it mean “stable” for you?
Thank you for voicing your concerns. To answer your last question: The fixes we make on the LTS branch are indeed fixed on the FTS branch as well if they are still applicable. Sorry for the late response, I had to confirm it with a few people on the team who were off for the holidays.
We typically engage the community with design decisions through discussions on GitHub and blog posts so the community knows why we do what. We are working on simplifying the version, naming, and packaging going forward. The branching on releases into FTS and LTS is meant to be a solution to address concern the community has had around naming, not another complication.
Is there a plan to add Office.Interop.Excel to available namespaces in .Net Core Class Library at any point in the future?
Thanks for opening the GitHub issue for this. (For those interested: https://github.com/dotnet/core/issues/402) O.I.E could be made compatible with .NET Core so you can reference it when working on Windows. I’m not sure if there were already plans to do this, but creating the issue is the best way to show interest. The issue should get more attention once everyone is back from the holidays.
Should we expect other Microsoft packages to follow this version scheme? I’m planning to stay on the LTS track, so I’m not sure if I should stick to 1.0.2 of Microsoft.AspNetCore.Mvc or upgrade to 1.1.0. I want to make sure I don’t miss any security fixes, but obviously being on LTS I don’t expect to get the latest features. I saw the comment about EntityFrameworkCore having an LTS track as well. I know 3rd party vendors will do their own thing, but is there a list of which Microsoft packages that follow this versioning scheme? Particularly Microsoft.EntityFrameworkCore, Microsoft.Extensions, and Microsoft.AspNetCore.
Yes, future LTS releases will follow this scheme. Security fixes are the main updates the LTS track gets so I wouldn’t worry about switching to FTS if you don’t mind waiting for the newer features. I am currently working on just such a table to help folks understand what package versions are associated with each .NET Core release. I’ll link it here once I’ve made it. (Probably after the holidays)