-
Notifications
You must be signed in to change notification settings - Fork 124
Discussion for nightly build 'Nightly - 6/17/16' #599
Comments
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 |
@peterblazejewicz thanks, still that's not very helpful. I think I'm more interested on details of:
|
I have a problem with nuget when create a class library project (portable) and setting .netstandard 1.5. 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 |
The release notes should be referencing the github issues. |
@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. |
The release notes say that this runtime doesn't support publishing to Azure "by default." What's the workaround to publish it anyway? |
thanks, I solved with that flag. Now I created a new asp.net core web app and recompiling I have this message
have I to add another nuget feed for these packages? |
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 = { This is on W10 x64. |
@drieseng try clearing your NuGet cache. There's been a lot of churn and rev'ing in-place:
And possibly uninstall/re-install the CLI tools after that? |
@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. |
@drieseng you can try opening an issue in the dotnet cli repo, that's probably the best way to investigate this issue further. |
Cleaning the local nuget cache did work for me, and i am no longer receive
I just used cmd "nuget locals all -clear" and restarted the VS. |
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. |
Closing this since the build this discussion is for is over a year old |
This is a discussion thread for pre-release build 'Nightly - 6/17/16'.
The text was updated successfully, but these errors were encountered: