Skip to content
This repository has been archived by the owner on Apr 11, 2020. It is now read-only.

Discussion for nightly build 'Nightly - 6/17/16' #599

Closed
balachir opened this issue Jun 20, 2016 · 16 comments
Closed

Discussion for nightly build 'Nightly - 6/17/16' #599

balachir opened this issue Jun 20, 2016 · 16 comments

Comments

@balachir
Copy link
Contributor

This is a discussion thread for pre-release build 'Nightly - 6/17/16'.

@Bartmax
Copy link

Bartmax commented Jun 20, 2016

Is there a list of issues resolved for each tooling version or anyway to get that info? Anything will do.

@peterblazejewicz
Copy link

Is there a list of issues resolved for each tooling version or anyway to get that info? Anything will do.

https://github.com/aspnet/Tooling#release-notes-and-known-issues

@Bartmax
Copy link

Bartmax commented Jun 20, 2016

@peterblazejewicz thanks, still that's not very helpful. I think I'm more interested on details of:

Includes a new pre-release .NET Core SDK (version 1.0.0-preview2-003041) and .NET Core (version 1.0.0-rc3-004459-00)

@ghost
Copy link

ghost commented Jun 21, 2016

I have a problem with nuget when create a class library project (portable) and setting .netstandard 1.5.
When open nuget manager in tab "installed" I see no package but a message "Error occurred"

The schema version of 'NETStandard.Library' is incompatible with version 2.11.1.812 of NuGet. Please upgrade NuGet to the latest version from http://go.microsoft.com/fwlink/?LinkId=213942.

I update neget with last version (3.0.5.1284) but I have some problem

@mikes-gh
Copy link

mikes-gh commented Jun 21, 2016

The release notes should be referencing the github issues.
The current release notes are just to vague for anyone with specific issues.
It seems once an issue goes -> TFSTracked we lose visibility from the outsidel

@balachir balachir changed the title Discussion for pre-release build 'Nightly - 6/17/16' Discussion for nightly build 'Nightly - 6/17/16' Jun 21, 2016
@lucamorelli
Copy link

lucamorelli commented Jun 22, 2016

I cannot install it in my test vm: I have this error message

untitled

Uninstalled the previous nightly and repaired the vs didn't solve the problem.

@balachir
Copy link
Contributor Author

@lucamorelli did you look at the Known Issues for this build? I suspect you are running into the known issue with the detection logic. The workaround is to run the EXE from a command prompt and then pass SKIP_VSU_CHECK=1 at the end. That should do the trick for you.

@clairernovotny
Copy link

The release notes say that this runtime doesn't support publishing to Azure "by default." What's the workaround to publish it anyway?

@lucamorelli
Copy link

lucamorelli commented Jun 23, 2016

thanks, I solved with that flag. Now I created a new asp.net core web app and recompiling I have this message

Severity    Code    Description 
Error   NU1002  The dependency Microsoft.AspNetCore.Mvc 1.0.0-rc3-21343 does not support framework .NETCoreApp,Version=v1.0.    
Error   NU1002  The dependency Microsoft.DotNet.Cli.Utils 1.0.0-preview2-003024 does not support framework .NETCoreApp,Version=v1.0.    
Error   NU1002  The dependency Microsoft.DotNet.ProjectModel.Loader 1.0.0-preview2-003024 does not support framework .NETCoreApp,Version=v1.0.  

have I to add another nuget feed for these packages?

@drieseng
Copy link

Since updating to this nightly, dotnet always yields the following error:

Failed to load the dll from [], HRESULT: 0x80070057

Enabling corehost tracing doesn't provide more info:

--- Invoked dotnet [version: 1.0.1, commit hash: cee57bf6c981237d80aa1631cfe83cb9ba329f12] main = {
dotnet
}
Failed to load the dll from [], HRESULT: 0x80070057
Load library of failed

This is on W10 x64.

@clairernovotny
Copy link

clairernovotny commented Jun 24, 2016

@drieseng try clearing your NuGet cache. There's been a lot of churn and rev'ing in-place:

nuget locals all -clear

And possibly uninstall/re-install the CLI tools after that?

@drieseng
Copy link

@onovotny This doesn't have anything to do with the NuGet cache. I get that error even when I run dotnet without any arguments. So even when I'm not trying to build or restore.

Clearing NuGet cache and re-install of the CLI tools had no effect.

@balachir
Copy link
Contributor Author

@drieseng you can try opening an issue in the dotnet cli repo, that's probably the best way to investigate this issue further.

@ghost
Copy link

ghost commented Jun 26, 2016

Cleaning the local nuget cache did work for me, and i am no longer receive

The schema version of 'NETStandard.Library' is incompatible with version 2.11.1.812 of NuGet. Please upgrade NuGet to the latest version from http://go.microsoft.com/fwlink/?LinkId=213942.

Also the error in nuget package manager "Error occurred" is gone and i see the installed packages.

I just used cmd "nuget locals all -clear" and restarted the VS.

@ghost
Copy link

ghost commented Jun 26, 2016

I got this Incompatible schema version message back again when I resumed the ReSharper in VS Options. I suspended again ReSharper and cleaned the local Nuget cache and I manage to get it working again.

I am using JetBrains ReSharper Ultimate 2016.2 EAP 5 Build 106.0.20160623.165258-eap5 and I have reported this to JetBrains.

@mlorbetske
Copy link

Closing this since the build this discussion is for is over a year old

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

9 participants