Core: .NET Core 1.0.1

[richlander]

You can read about .NET Core 1.0.1 in the announcement: Announcing September 2016 Updates for .NET Core 1.0.

Please report any issues you find with .NET Core 1.0.1 here, 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

[zeusro]

Couldn't use normally

[root /]# dotnet

Microsoft .NET Core Shared Framework Host

  Version  : 1.0.1
  Build    : cee57bf6c981237d80aa1631cfe83cb9ba329f12

Usage: dotnet [common-options] [[options] path-to-application]

Common Options:
  --help                           Display .NET Core Shared Framework Host help.
  --version                        Display .NET Core Shared Framework Host version.

Options:
  --fx-version <version>           Version of the installed Shared Framework to use to run the application.
  --additionalprobingpath <path>   Path containing probing policy and assemblies to probe for.

Path to Application:
  The path to a .NET Core managed application, dll or exe file to execute.

If you are debugging the Shared Framework Host, set 'COREHOST_TRACE' to '1' in your environment.

To get started on developing applications for .NET Core, install .NET SDK from:
  http://go.microsoft.com/fwlink/?LinkID=798306&clcid=0x409

Exit code: 129
[root /]# uname -a
Linux localhost.localdomain 2.6.32-042stab111.11 #1 SMP Tue Sep 1 18:19:12 MSK 2015 x86_64 x86_64 x86_64 GNU/Linux
[root /]# dotnet version
Failed to load /opt/dotnet/shared/Microsoft.NETCore.App/1.0.1/libcoreclr.so, error: libunwind.so.8: cannot open shared object file: No such file or directory
Failed to bind to CoreCLR at '/opt/dotnet/shared/Microsoft.NETCore.App/1.0.1/libcoreclr.so

error: libunwind.so.8: cannot open shared object file: No such file or directory

[richlander]

Thanks @zeusro. I cannot tell which distro you are using from your uname command above. Can you share that?

[Thaoden]

OS version

Win 10 Enterprise 1511

Repro steps

Opening a solution in Visual Studio 2015 Professional Update 3

Error messages

The following error occurred attempting to run the project model server process (1.0.0-preview2-003131).
No connection could be made because the target machine actively refused it [::ffff:127.0.0.1]:51753.
The project model server process provides intellisense, build, and reference information to Visual Studio and without it your experience will be very limited. Please try closing and reopening Visual Studio to see if that corrects the problem. Alternatively, check that the .NET core SDK is properly installed.

Whether this worked before

It did.

Method of installing .NET Core

Using the downloader available here.

Using the SDK installer available on the same page to Repair the SDK seems to have fixed it.

[zeusro]

@richlander

[root /]# cat /proc/version
Linux version 2.6.32-042stab111.11 ([email protected]) (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Tue Sep 1 18:19:12 MSK 2015

[root /]# getconf LONG_BIT
64

[root /]# cat /etc/redhat-release
CentOS Linux release 7.2.1511 (Core) 

[agoretsky]

Windows 10, install from https://www.microsoft.com/net/core#windows.
During installation I am getting error:

dd_DotNetCoreTools__20160914112850.log.txt

[webprofusion-chrisc]

If I upgrade my project to 1.0.1 via nuget, then rebuild and deploy to production IIS server (with latest DotNetCore 1.0.1 Windows Hosting package installed) I get HTTP Error 502.5 - Process Failure - running the compiled .exe for the app reveals that it can't find Microsoft.AspnetCore.Server.Kestrel, Version 1.0.0 , so something is hanging on to the old reference. Kestrel 1.0.1 is reference in the project.json.

[svick]

@webprofusion-chrisc How does your project.json look like?

[webprofusion-chrisc]

project.json: https://gist.github.com/webprofusion-chrisc/acf9f999be369e7ec94d310e9080a5c4

May be a little unusual as it's basically using dotnet 4.6 due to other dependencies (Soap stuff)

Update: note that it works fine under IIS Express on dev machine, it's after deployment to Server 2008 R2 with IIS that the issue occurs.

[webprofusion-chrisc]

Ok, resolved for me. I hadn't installed the updated VS2015 tooling, although I'd updated my nuget packages in the solution and hosting bundle on the server. I'd tried reverting to 1.0.0 of the Kestrel and MVC assemblies and that obviously worked. After installing the VS tooling update I updated my nuget packages back to 1.0.1 and it worked in production.

Update 1: it appears the difference was the generate .exe.config after the tooling update now adds the bindingRedirect entries for EntityFrameworkCore

[h3smith]

I maybe missing it somewhere, but it maybe useful to add some instructions of what exactly need to be updated as versions get upgraded. I bumped the versions from 1.0 to 1.0.1 and had a litany of build issues (had to make sure VS and CLI were updated, as well as project.json changes)

Just to help streamline the process?

[webprofusion-chrisc]

When upgrading another project I found that to get it to build I needed to add a runtimes section to the project.json:

"runtimes": { "win7-x64": {} }

The project was previously building and working in production without that.

[MarcelWouters]

Running Asp.Net MVC Core project in Visual Studio 2015 with Update 3 I get:

_The program '[9412] dotnet.exe' has exited with code -2147450749_

When I changed the setting

"Microsoft.NETCore.App": {
"version": "1.0.1",
"type": "platform"
},

back to version 1.0.0 the web app runs in IIS Express. I followed this blog for updating my project: https://blogs.msdn.microsoft.com/dotnet/2016/09/13/announcing-september-2016-updates-for-net-core-1-0/

[jamesabolton]

I have the same problem as @webprofusion-chrisc. After reading the changelog I didn't see anything indicating this was required. I rolled back to v1.0.0 and I am still forced to provide the runtimes section in project.json

Edit 1: change this in project.json after changing the packages to 1.0.1
"Microsoft.NETCore.App": "1.0.1"
to
"Microsoft.NETCore.App": { "version": "1.0.0", "type": "platform" }

To avoid adding runtimes section using 1.0.1 change
"Microsoft.NETCore.App": "1.0.1"
to
"Microsoft.NETCore.App": { "version": "1.0.1", "type": "platform" }

[Petermarcu]

@DamianEdwards @piotrpMSFT @livarcocc , Any of you guys know what may have changed to cause a required runtimes section?

[blackdwarf]

@zeusro did you install all of the required dependencies?

[DamianEdwards]

My hunch is perhaps they're hitting the issue where the NuGet VS tooling drops the "type": "platform" from the reference, which effectively changes the project to stand-alone and thus would force the requirement of a runtimes section.

[Petermarcu]

Yeah, that would do it. @yishaigalatzer do you know why the nuget tooling is doing that?

[yishaigalatzer]

I don't know the root cause @emgarten should be able to take a look. My guess is that we require a rid restore where before there was an implicit rid running in restore based on the machine you run on

[emgarten]

Updating through the NuGet UI calls into the project system to update project.json, "type": "platform" is dropped during that edit. NuGet 3.5.0 RTM (not released yet) will have a workaround for this issue.

[Petermarcu]

@richlander , do we have a known issues list for the release?

[h3smith]

on macOS Sierra, (fresh install) the latest installer didn't set the correct path - dotnet in terminal returned command not found

OS version
macOS Sierra
Repro steps
Fresh install of macOS without prior dotnet core
Repro code (if you can share it / is relevant)
Error messages
command not found
Whether this worked before
Method of installing .NET Core
package installer

Ran

ln -s /usr/local/share/dotnet/dotnet /usr/local/bin

and started working

[richlander]

@Petermarcu Known issues would appear here: https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.1-release-notes.md. There are not any listed yet.

/cc @leecow

[blackdwarf]

@h3smith which shell are you using? Also, can you please check if the /etc/paths.d/dotnet file is in its place?

[chrisgreen42]

OS Version:
Windows 8.1 Enterprise
Repro Steps:
Updating .NetCore.App in existing project via Nuget.

Similar issue occurs as @jamesabolton reported and have to edit the project.json file as described. However, IIS Express would not launch when trying to debug. in 1.0.1 When I rolled back to 1.0.0, IIS Express would launch.

[jamesabolton]

@chrisgreen42 I started having the same issue. I brought up a command prompt, navigated to my project's folder and tried to run the web app:

E:\Programming\GitHub\HuskyRescueCore\src\HuskyRescueCore>dotnet run
Project HuskyRescueCore (.NETCoreApp,Version=v1.0) was previously compiled. Skipping compilation.
The specified framework 'Microsoft.NETCore.App', version '1.0.1' was not found.
  - Check application dependencies and target a framework version installed at:
      C:\Program Files\dotnet\shared\Microsoft.NETCore.App
  - The following versions are installed:
      1.0.0
  - Alternatively, install the framework version '1.0.1'.

At that point I realized I didn't actually install 1.0.1 which you can get here. Now I can debug via VS again.

[zeusro]

@blackdwarf Do you mean libunwind,libicu?YES,I followed the steps as https://www.microsoft.com/net/core#centos says.

sudo yum install libunwind libicu
curl -sSL -o dotnet.tar.gz https://go.microsoft.com/fwlink/?LinkID=827529
sudo mkdir -p /opt/dotnet && sudo tar zxf dotnet.tar.gz -C /opt/dotnet
sudo ln -s /opt/dotnet/dotnet /usr/local/bin

[MarcelWouters]

Solution of @chrisgreen42 worked for me. Installed .NET Core Installer x86 and debugging works in Visual Studio.

[stevejgordon]

Since installed .NET 1.0.1 I am having problems working on a project still targeting 1.0.0.

I am using 1.0.1 successfully in some solutions but an open source project https://github.com/HTBox/allReady still targets the prior release in our master branch.

OS is Windows 7

When trying to debug the application from VS 2015 I get the following error:

System.IO.FileLoadException was unhandled
Message: An unhandled exception of type 'System.IO.FileLoadException' occurred in Unknown Module.
Additional information: Could not load file or assembly 'Microsoft.AspNetCore.Server.Kestrel, Version=1.0.1.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

The application is targeting Kestrel 1.0.0 in the project.json

I don't believe there are any other changes except for the install of .NET core. I've tried deleting the packages folder and local nuget cache with no improvement.

[stevejgordon]

Further to my recent comment after upgrading the project to use 1.0.1 it runs. This is not ideal though since until the project formally moves to this version I can only work on it by adjusting my dependencies and avoiding checking them in.

[blackdwarf]

@ellismg did we up the libunwind version number by any chance for 1.0.1, do you know?

[ellismg]

@blackdwarf No. I don't believe there were any changes in native dependencies or their versions for 1.0.1

[nicodewet]

This is surely a case of RTFM & PEBKAC. That said, when it comes to "dotnet run", if NuGet cannot and will not magically update 'Microsoft.NETCore.App' and gives you the message "Alternatively, install the framework version '1.0.1'", this is to suggest that the command reminds the user that they need to download the necessary installer. I got stuck in a headspin wondering why NuGet has failed me on my Mac.

In terms of the installer, I'd put the version number in the name, dotnet-dev-osx-x64.1.0.0-preview2-003131.pkg installs "Microsoft .NET Core 1.0.1 - SDK Preview 2-003131 (x64)".

[dromanchenko]

i had the same problem as @webprofusion-chrisc. The solution was to add a binding redirect for Microsoft.AspNetCore.Server.Kestrel. My project is an empty asp.net core app (no mvc dependencies at all)

[3ropka]

1) OS: Linux version 4.7.0-kali1-amd64 ([email protected]) (gcc version 5.4.1 20160803 (Debian 5.4.1-1) ) #1 SMP Debian 4.7.5-1kali3 (2016-09-29)

dotnet:

Product Information:
 Version:            1.0.0-preview2-003131
 Commit SHA-1 hash:  635cf40e58

2) dotnet restore => Segmentation fault

(gdb) run
Starting program: /usr/local/bin/dotnet restore
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff47c7700 (LWP 5540)]
[New Thread 0x7ffff3fc6700 (LWP 5541)]
[New Thread 0x7ffff37c5700 (LWP 5542)]
[New Thread 0x7ffff2fc4700 (LWP 5543)]
[New Thread 0x7ffff27c3700 (LWP 5544)]
[New Thread 0x7ffff1c49700 (LWP 5545)]
[New Thread 0x7fffe20c7700 (LWP 5546)]
[New Thread 0x7fffe18c6700 (LWP 5547)]
[New Thread 0x7fffe10c5700 (LWP 5548)]
[New Thread 0x7fffe08c4700 (LWP 5549)]
[New Thread 0x7fffe00c3700 (LWP 5550)]
[New Thread 0x7fffdf8c2700 (LWP 5551)]
[New Thread 0x7fff5cfab700 (LWP 5552)]
[New Thread 0x7fff3ffff700 (LWP 5553)]
[Thread 0x7fff3ffff700 (LWP 5553) exited]
log  : Restoring packages for /home/****/*****/MyFirstApp/project.json...

Thread 14 "dotnet" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff5cfab700 (LWP 5552)]
0x00007fffe24a2ddd in ?? () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0

cat project.json

{
  "version": "1.0.0-*",
  "buildOptions": {
    "debugType": "portable",
    "emitEntryPoint": true
  },
  "dependencies": {},
  "frameworks": {
    "netcoreapp1.0": {
      "dependencies": {
        "Microsoft.NETCore.App": {
          "type": "platform",
          "version": "1.0.1"
        }
      },
      "imports": "dnxcore50"
    }
  }
}

4) Problem also exists on 4.3 kernel.
5) dotnet installed via:

    sudo apt-get install curl libunwind8 gettext
    curl -sSL -o dotnet.tar.gz https://go.microsoft.com/fwlink/?LinkID=827530
    sudo mkdir -p /opt/dotnet && sudo tar zxf dotnet.tar.gz -C /opt/dotnet
    sudo ln -s /opt/dotnet/dotnet /usr/local/bin

[chrisdrobison]

I'm seeing the following error on VS 2015. I've uninstalled all the SDKs and tooling packages and reinstalled just the latest and I'm still seeing this.

[chrisdrobison]

I figured it out. It looks like JustMock gets in the way. I had to disable it and then this error went away.

[antonfirsov]

I had similar issue with an existing project after installing VS 2017 RC.
For me the solution was adding˛"sdk": {"version": "1.0.0-preview2-003131"} to global.json
(Maybe this helps some googler in the future)

[Petermarcu]

Closing this and pointing to 1.0.2. https://github.com/dotnet/core/issues/294