.Net Standard 2.1

Elements EBuild
1

Hi,
Ive installed the latest core and it gives me .net standard 2.1 in the target framework dropdown in Fire. If I try and build it fails with an error about unsupported schema

standard21.txt (16.7 KB)

Thanks,
John

2

It doesnt seem installed, the files arent in .nuget.

I guess its trying to find it and falls back to the that last folder and doesnt like the format

Checking <NuGetRepository file:///Users/JohnMoshakis/.nuget/packages/>
D: Package NETStandard.Library found in repository <NuGetRepository file:///Users/JohnMoshakis/.nuget/packages/>
D: Available Versions of ‘NETStandard.Library’: 2.0.0-preview1-25301-01, 2.0.0-preview1-25212-02, 2.0.0, 1.6.1, 1.6.0, 1.5.0-rc2-24027.
D: Package NETStandard.Library version 2.1 could not be matched in repository <NuGetRepository file:///Users/JohnMoshakis/.nuget/packages/>.
D: Checking <NuGetRepository :///Users/JohnMoshakis/.dotnet/NuGetFallbackFolder>

3

Checking <NuGetRepository :///Users/JohnMoshakis/.dotnet/NuGetFallbackFolder>

This doesn’t seem like a valid url?

4

No. Im not sure where its coming from.

Im trying to convert an older project to use NuGetReference

5

Is it because it cant find a package ?

         Package Microsoft.Owin.Host.SystemWeb:3.0.1 found in local cache.

D: Checking <NuGetRepository file:///Users/JohnMoshakis/.nuget/packages/>
D: Checking <NuGetRepository https://api.nuget.org/v3/index.json>
D: Checking <NuGetRepository :///Users/JohnMoshakis/.dotnet/NuGetFallbackFolder>
E: Unsupported URL scheme
D: | at RemObjects.Elements.Basics.PackageRepository.HasPackageWithName (System.String aName) [0x00066] in :0 .
D: | at RemObjects.Elements.Basics.NuGetRepository.HasPackageWithName (System.String aName) [0x00043] in :0 .
D: | at RemObjects.EBuild.Elements.ElementsProcessNuGetReferences.FindConcretePackageWithName (System.String aName, System.String aVersion) [0x00124] in <02efa3fab0a6401a8aed927f46a2989c>:0 .
D: | at RemObjects.EBuild.Elements.ElementsProcessNuGetReferences.ProcessNuGetReference (RemObjects.EBuild.EBuildObject aReference) [0x00074] in <02efa3fab0a6401a8aed927f46a2989c>:0 .
D: | at RemObjects.EBuild.Elements.ElementsProcessNuGetReferences.Execute () [0x0013a] in <02efa3fab0a6401a8aed927f46a2989c>:0 .
D: | at RemObjects.EBuild.EBuildContext.RunTask________forTarget (RemObjects.EBuild.EBuildTask+MetaClass aTask, RemObjects.EBuild.EBuildValues aSettings, RemObjects.EBuild.EBuildObjects aObjects, RemObjects.EBuild.EBuildTarget aTarget) [0x0030b] in <5185432fc9d54b73acb1640af3d69f6b>:0 .
<- Task RemObjects.EBuild.Elements.ElementsProcessNuGetReferences failed with exception Unsupported URL scheme for SailingLogWebApplication, Echoes, took 0.0000s (1.6569s).
D: | at RemObjects.Elements.Basics.PackageRepository.HasPackageWithName (System.String aName) [0x00066] in :0
D: | at RemObjects.Elements.Basics.NuGetRepository.HasPackageWithName (System.String aName) [0x00043] in :0
D: | at RemObjects.EBuild.Elements.ElementsProcessNuGetReferences.FindConcretePackageWithName (System.String aName, System.String aVersion) [0x00124] in <02efa3fab0a6401a8aed927f46a2989c>:0
D: | at RemObjects.EBuild.Elements.ElementsProcessNuGetReferences.ProcessNuGetReference (RemObjects.EBuild.EBuildObject aReference) [0x00074] in <02efa3fab0a6401a8aed927f46a2989c>:0
D: | at RemObjects.EBuild.Elements.ElementsProcessNuGetReferences.Execute () [0x0013a] in <02efa3fab0a6401a8aed927f46a2989c>:0
D: | at RemObjects.EBuild.EBuildContext.RunTask________forTarget (RemObjects.EBuild.EBuildTask+MetaClass aTask, RemObjects.EBuild.EBuildValues aSettings, RemObjects.EBuild.EBuildObjects aObjects, RemObjects.EBuild.EBuildTarget aTarget) [0x0030b] in <5185432fc9d54b73acb1640af3d69f6b>:0

6

It seems somehow you have 3 repositories registered.

can you check what’s in

~/.nuget/NuGet/NuGet.config under the packageSources key for me? I read those and create URLs, it seems to me that maybe Microsoft is mixing URLs and file paths, which could cause this…

I’ll add a workaround.

7

And up, as develop-20181226-124252 - 6929ee7.

1 Like
8

I have this

<?xml version=“1.0” encoding=“utf-8”?>

<configuration>

<packageSources>

<add key=“nuget.org” value=“https://api.nuget.org/v3/index.json” protocolVersion=“3” />

<add key=“CliFallbackFolder” value="/Users/JohnMoshakis/.dotnet/NuGetFallbackFolder" />

</packageSources>

</configuration>

9

K, that’d do it. I expected these to consistently be URLs. the new build should fix it.

10

This appears to be broken in the latest. I get this

D: Checking <NuGetRepository https://api.nuget.org/v3/index.json>
D: Package NETStandard.Library found in repository <NuGetRepository https://api.nuget.org/v3/index.json>
D: Available Versions of ‘NETStandard.Library’: 2.0.3, 2.0.2, 2.0.1, 2.0.0, 2.0.0-preview2-25401-01, 2.0.0-preview1-25301-01, 1.6.1, 1.6.1-preview1-24530-04, 1.6.0, 1.5.0-rc2-24027.
D: Package NETStandard.Library version 2.1 could not be matched in repository <NuGetRepository https://api.nuget.org/v3/index.json>.
D: Checking <NuGetRepository file:///Users/JohnMoshakis/.dotnet/NuGetFallbackFolder/>
D: Package NETStandard.Library found in repository <NuGetRepository file:///Users/JohnMoshakis/.dotnet/NuGetFallbackFolder/>
D: Available Versions of ‘NETStandard.Library’: 2.0.0-preview1-25301-01, 1.6.1, 1.6.0.
D: Package NETStandard.Library version 2.1 could not be matched in repository <NuGetRepository file:///Users/JohnMoshakis/.dotnet/NuGetFallbackFolder/>.
E: Package NETStandard.Library matching version 2.1 was not found in any repositories.
<- Task RemObjects.EBuild.Elements.ElementsProcessNuGetReferences failed for GitHubGraphQL, Echoes, took 2.1242s (2.1243s).

11

yeah, looks like 2.1 still uses the 2.0.3 library. I wish there was any rules, rhyme or reason to what Microsoft is doing here… Fixed for vNext.

1 Like
12

Workaround for now would be to add an explicit reference to the 2.0.3 version.

13

I tried with the latest and its finding 2.1 but doesnt recognize IAsyncEnumerable

The docs says it should be available

AsyncSequences.zip (597.6 KB)

14

Hmm. maybe going back to 2.0.3 is the wrong approach and they rename packages again. What package does VC# pull in? I’ll do some digging on my side, too.

15

hmm, there IS a NETStandard.Library.Ref, which matches the renaming they did for .NET Core 3.0. So using that is probably the proper fix (done)

That said, even if I use that, I still get Unknown type "IAsyncEnumerable"…

D: Available Versions of ‘NETStandard.Library.Ref’: 2.1.0, 2.1.0-rc1-19456-20, 2.1.0-preview9-19423-09, 2.1.0-preview8-28405-07, 2.1.0-preview7-27912-14, 2.1.0-preview6-27804-01, 2.1.0-preview5-27626-15, 2.1.0-preview4-27615-11.
D: Package NETStandard.Library.Ref:2.1.0 found in repository <NuGetRepository https://api.nuget.org/v3/index.json>.

16

Nevermind, works. The error i got for not specifying the namespace properly is just wrong, which I’ll log separately.

17

(BTW, in Oxygene you can also use async sequence of T)