Sdk: How to use daily sdk build with daily ASP.NET Core build

Created on 30 Jan 2018  路  23Comments  路  Source: dotnet/sdk

Steps to reproduce

Download and untar latest sdk from https://github.com/dotnet/cli

dotnet new web
dotnet run

Expected behavior

I can get the application to run based on README info

Actual behavior

It was not possible to find any compatible framework version
The specified framework 'Microsoft.AspNetCore.All', version '2.1.0-preview1-28124' was not found.
  - Check application dependencies and target a framework version installed at:
      /home/tmds/Downloads/dotnet-sdk-latest/
  - The .NET framework can be installed from:
      https://aka.ms/dotnet-download-runtime
  - The .NET framework and SDK can be installed from:
      http://go.microsoft.com/fwlink/?LinkID=798306&clcid=0x409

Environment data

.NET Command Line Tools (2.1.300-preview2-008022)

Product Information:
 Version:            2.1.300-preview2-008022
 Commit SHA-1 hash:  71f22a9f37

Runtime Environment:
 OS Name:     fedora
 OS Version:  25
 OS Platform: Linux
 RID:         fedora.25-x64
 Base Path:   /home/tmds/Downloads/dotnet-sdk-latest/sdk/2.1.300-preview2-008022/

Microsoft .NET Core Shared Framework Host

  Version  : 2.1.0-preview1-26116-04
  Build    : eeb3a84e2142aba791fe003564b8afd048c45ff9
Bug

All 23 comments

@natemcmaster is this due to some mismatch between the templates and the CLI?

Possibly. @tmds what's in the generated csproj file? Also what is in /home/tmds/Downloads/dotnet-sdk-latest/shared/?
cc @JunTaoLuo

From the error message it looks like there was no aspnetcore shared framework installed at all. Which sdk installer was used? I took a quick look at the OSX tar.gz file and it did include the aspnetcore shared framework.

Indeed, I don't see the shared framework in the file linked above.

@natemcmaster @JunTaoLuo is this something that you guys can take a look at? Probably something missing in the build files from when we ingested the asp.net shared framework in the SDK.

It should be installed under shared/. There's something wrong with the linux archive. The osx and windows archives contain Microsoft.AspNetCore.All under the correct directory.

Btw the Microsoft.AspNetCore.App package that was introduced in the announcement post (https://github.com/aspnet/Announcements/issues/287) also requires a shared framework.

Is this supposed to be a change in an upcoming update or will both packages + shared frameworks be included in an upcoming cli?

Correct, we have already built that package and shared framework on our side. It will be included in the cli soon.

FYI - you can also get installers for the aspnetcore shared framework here: https://github.com/aspnet/universe#daily-builds. The versions linked their may not match with what is bundled in the CLI. There is a lag between when we produce a new build of aspnetcore and when CLI consumes it.

@livarcocc @johnbeisner I took a look at our builds and it seems like we produced all the required artifacts for the 28124 build that was ingested by the CLI so I'm not sure why the linux archive didn't pick it up. Can you look through the build logs for the 26116-04 build or point me to where the build log is?

Can you look through the build logs for the 26116-04 build or point me to where the build log is?

@livarcocc @johnbeisner ping

This is the CLI build for the Linux portable TAR: https://devdiv.visualstudio.com/DevDiv/Default/_build/index?buildId=1331328&_a=summary
you should find the download link for the logs near the top

@JunTaoLuo

This dropped off my radar last week. I just took a look at the build log and it seems the aspnetcore-runtime artifacts were being downloaded and extracted.

2018-01-29T21:37:59.9504620Z          /bin/tar xf /opt/code/bin/2/linux-x64/packages/aspnetcore-runtime-internal-2.1.0-preview1-28124-linux-x64.tar.gz -C /opt/code/bin/2/linux-x64/intermediate/sharedFrameworkPublish 

This suggests that our artifacts were being picked up but I'm not sure why they were not included in the sdk archives. Could this be similar to the issue with the mac pkg installers were outdated builds steps weren't picking up our new shared framework? https://github.com/dotnet/cli/pull/8539

cc @Eilon @livarcocc this also seems like also a blocking-release issue. The dotnet-sdk-linux-x64.tar.gz file does not include the aspnetcore runtime. I'm trying to see if dotnet/cli#8539 fixes it as well.

Assigning myself to take a closer look at this

@livarcocc could you also take a look? This is blocking one of @balachir's scenarios: Installing the CLI/SDK with tar.gz archive and do a restore locally.

Looking...

I manually verified all .zips and .tar.gz's from product build 20180205-02-1360785 include the aspnetcore shared runtime.

Recommend closing this now once dotnet/cli#8539 makes it back to master.

NIT: "Recommend closing this now once https://github.com/dotnet/cli/pull/8539 & https://github.com/dotnet/cli/pull/8552 makes it back to master."

Do we know why it was missing in previous builds? I don't know if closing this issue without knowing why the problem occurred in the first place is a good idea.

When updating the code from the package runtime store to the shared framework, I missed this required change to redist.csproj: https://github.com/dotnet/cli/commit/8de55145af7724b9af261dec4c4090e98117c4a5#diff-acadc45977478b307ad6d53f23f6e17c

The fix should be in master now.

Was this page helpful?
0 / 5 - 0 ratings