Core: .NET Core 1.1.0

[leecow]

[Renaming and updating this issue to the final 1.1 release]

You can read about .NET Core 1.1 in the blog post: Announcing .NET Core 1.1 and download the update from the .NET Core install page now.

Please report any issues you find with .NET Core 1.1 in this repo, either responding to this issue or creating a new issue.

Please include the following information plus any other info that you think is relevant:

OS version
Repro steps
Repro code (if you can share it / is relevant)
Error messages
Whether this worked before
Method of installing .NET Core

[vaindil]

Is that blog post supposed to be live? There's nothing on the .NET blog about 1.1.0.

EDIT: Since posting this comment the article has been posted. Thanks!

[MartinJohns]

The current design is that dotnet new will create new projects for the latest .NET Core version installed. If you don’t think that’s the right choice, tell us what you would like to see.

I think it should be the latest stable .NET Core version installed.

[kamcma]

Since the release notes say nothing about it, I'm assuming this preview does _not_ remove the OpenSSL dependency in macOS?

[aggieben]

Chiming in on the dotnet new thing: why couldn't it be user-determined via command line switch? i.e., dotnet new --sdk 1.1? If we had that, having it pick the latest as the default would be just fine.

[bartonjs]

@kamcma The OpenSSL dependency is _reduced_, but not removed. There's still quite a lot of work left, crypto's big :smile:. https://github.com/dotnet/corefx/issues/9394 is the work/tracking issue.

[vaindil]

The packages referenced in the release notes for Ubuntu downloads do not exist, at least in the xenial repository. Also the 16.10 section says Ubunt. :P

$ apt-cache search dotnet
libgtk2.0-cil - CLI binding for the GTK+ toolkit 2.12
libgtk2.0-cil-dev - CLI binding for the GTK+ toolkit 2.12
libgtk-dotnet3.0-cil - GTK.NET library
libgtk-dotnet3.0-cil-dev - GTK.NET library - development files
dotnet-dev-1.0.0-preview2-003121 - Microsoft .NET Core 1.0.0 - SDK Preview 2
dotnet-dev-1.0.0-preview2-003131 - Microsoft .NET Core 1.0.1 - SDK 1.0.0 Preview 2-003131
dotnet-dev-1.0.0-preview2.1-003155 - Microsoft .NET Core 1.1.0 Preview1 - SDK 1.0.0 Preview 2.1-003155
dotnet-host - Microsoft .NET Core 1.1.0 - Host
dotnet-hostfxr-1.0.1 - Microsoft .NET Core 1.0.0 - Host FX Resolver 1.0.1
dotnet-hostfxr-1.1.0-preview1-001100-00 - Microsoft .NET Core 1.1.0 - Host FX Resolver 1.1.0-preview1-001100-00
dotnet-sharedframework-microsoft.netcore.app-1.0.0 - Microsoft .NET Core 1.0.0 - Runtime Microsoft.NETCore.App 1.0.0
dotnet-sharedframework-microsoft.netcore.app-1.0.1 - Microsoft .NET Core 1.0.1 - Runtime Microsoft.NETCore.App 1.0.1
dotnet-sharedframework-microsoft.netcore.app-1.1.0-preview1-001100-00 - Microsoft .NET Core 1.1.0 - Runtime Microsoft.NETCore.App 1.1.0-preview1-001100-00

[leecow]

@vaindil Added package refs to the install page. Let me know if that's the right idea. Also fixed Ubunt ;-)

[vaindil]

@leecow Helpful, definitely, but not quite the problem. Instructions say to run this command:

sudo apt-get install dotnet-sdk-ubuntu.16.04-x64.1.0.0-preview2.1-003155

but that package does not exist so the command fails. I believe the correct command should be:

sudo apt-get install dotnet-dev-1.0.0-preview2.1-003155

Installing that package resolved the error I was getting about 1.1.0 not being installed.

[leecow]

@vaindil Gotcha ... will fix that.

[tanaka-takayoshi]

dotnet new doesn't work on Fedora 24.

• OS version

$ cat /etc/fedora-release Fedora release 24 (Twenty Four)

• Repro steps

$ dotnet new Failed to initialize CoreCLR, HRESULT: 0x80131500

• Repro code (if you can share it / is relevant)
  N/A
• Error messages
  Failed to initialize CoreCLR, HRESULT: 0x80131500
• Whether this worked before
  Fedora 24 is newly supported at .NET Core 1.1 preview.
• Method of installing .NET Core
  https://github.com/dotnet/core/blob/master/release-notes/preview-download.md#installation-from-a-binary-archive

$ wget https://go.microsoft.com/fwlink/?LinkID=831489 -O dotnet.gz $ sudo mkdir -p /opt/dotnet $ sudo tar zxf dotnet.gz -C /opt/dotnet $ sudo ln -s /opt/dotnet/dotnet /usr/local/bin

[leecow]

Apologies for that @tanaka-takayoshi ! Fedora 24 support did not make it into the Preview release but I have confirmed that it's in for the final release.

From the core-setup repo:

git shortlog -n --format="%h %cd %s" | grep "edora 24"
      13a1fce Mon Oct 24 13:20:22 2016 -0700 Add build logic and packaging for Fedora 24
      7aab2f7 Mon Oct 24 13:30:05 2016 -0700 Small modifications to enable fedora 24 build
      2ac2d09 Tue Oct 25 15:38:49 2016 -0700 Add handling for Fedora 24 in some build code.

[tanaka-takayoshi]

@leecow Thanks for the confirmation. I'm looking forward to the final release.

[Ponant]

dotnet new produces the correct project.json, but creating a new ASP.NET Core (Core) from VS 2015 will generate the older 1.0 project.json; is that expected?

[M-Curtis]

Windows 10
Create a new ASP .Net Core Web Application, update all template packages to prerelease.
When running the page even with nothing changed the output window displays the errors
The program '[yyyy] dotnet.exe' has exited with code -2147450749 (0x80008083). The program '[xxxx] iisexpress.exe' has exited with code 0 (0x0).
Yeah since then I've not been able to get my IIS to work even when deleting the IISExpres folder in documents and rebooting PC

Edit: Yeah IIS doesn't work now even when downgrading all packages to stable release

Second Edit: For anyone else that does get this problem, I managed to fix it by going into my bin/debug/netcoreapp1.0 folder and deleting all files in there then deleting project.json and project.lock.json and copying in a fresh asp.net core template, project.json and project.lock.json and after restoring packages I no longer got this error.

[leecow]

@Ponant - yes, that's expected until the upcoming Dev15 RC and .NET Core / ASP.NET Core update.

[danroth27]

@M-Curtis Sounds like there was an issue with the modified project.json file. If you can share the problematic project.json file with us we can take a look and see what might be amiss.

[Jacfal]

Hi, OpenSUSE 42.1 link on ".NET Core 1.1 Preview 1 and .NET Core SDK 1.0 Preview 2.1" (core/release-notes/preview-download.md) page is wrong. Link refers to the version without sdk. Can you fix it?

[rhires]

Feedback was requested on the "dotnet new" design choice for it using Preview 1 instead of 1.0. I think that perhaps you should add a command line option parameter for a version number if the default is _not_ the choice you want. So "dotnet new" would give you the default most recent installed version, but if I explicitly want 1.0, then I can type "dotnet new --version 1.0" . As I write this, it seems roughly similar to dnvm. Maybe we could have that back in some form?

[leecow]

Thanks for letting us know about the bad link @Thunderchie-f. Download page has been updated.

[leecow]

@rhires, thanks for the feedback. This is inline with discussions we having to Include some gesture to choose what version to target with dotnet new. Will add your vote!

/cc @richlander

[Petermarcu]

@tanaka-takayoshi Try this for bleeding edge Fedora 24 binaries.

[tanaka-takayoshi]

@Petermarcu Thanks, but it doesn't include dotnet SDK, only runtime. So I could try few things.

[Petermarcu]

@tanaka-takayoshi , yeah, its definitely bleeding edge. You can use the existing SDK's on other runtimes. You can likely replace the contents of dotnet/shared/Microsoft.NETCore.App/1.0.1 with the contents from that tar.gz and it should work.

[BalassaMarton]

Using the 1.1.0 version of Microsoft.NETCore.App from the ASP.NET vNext myget feed (https://www.myget.org/F/aspnetvnext/api/v2) definitely causes this problem:

The program '[xxxx] dotnet.exe' has exited with code -2147450749 (0x80008083).
The program '[yyyy] iisexpress.exe' has exited with code 0 (0x0).

UPDATE: The official 1.1.0 packages are working without problems of course.

[VahidN]

Is there a new version of the IIS Hosting module for .NET Core 1.1 RTM?
I could find only this old page which is not for Windows Server Hosting 1.1 RTM.

[shirhatti]

@VahidN There is a new version of the ASP.NET Core Module for IIS for .NET Core 1.1 RTM. The download link is listed on https://www.microsoft.com/net/download/core

[CodingSamurai]

I was getting the same issue as @BalassaMarton when using the upgrade via NuGet functionality in Visual Studio. Had to rollback the upgrade.

[richlander]

Closing this one. Please move to the latest release: #532.

[Indyy66]

I have an app using .net core 1.1.0 and having a hell of a time getting the polyfills.ts file to be picked up by webpack or any part of the compile system. The application is required to work with IE11 and is currently hindered because of this issue. I would say that my biggest issue, is where to place the file polyfills.ts in the project so that it will be compiled and bundled with the rest of the application?

Server setup is Windows server 2012 with IIS 8.0, Development machine is Windows 10 with IIS 8.5.
The development tool is VS2017 latest updates 15.3+.