NetStandard Library for UWP app

[ndelic]

I’m trying to add a NetStandard class library project (Silver) to UWP app project (Visual C#). Both projects are in the same solution. I changed target of the class library to .NET Standard 2.0 and tried to add the NetStandard.Library nuget package, but Visual Studio wouldn’t install it.

If I add the nuget package reference to the .elements project file manually, and then try to add my library as UWP project reference again, VS 2017 says it can’t add it. If I create a Visual C# NetStandard class library I can add it to the UWP project without any problems.

Using VS2017 with Elements/Silver .2373.

Does anybody have any experience with that?

[mh (marc hoffman)]

Niko,

can you clarify what exactly fails?

I gather you have two projects:

• an Elements Library project, set to build for .NET Standard 2.0 (using Silver, but that’s irrelevant)
• an Visual C# UWP project

Is the problem adding a reference to the library project to from the UWP app? or adding an (unrelated) NuGet reference to the .NET Standard library? What are the exact steps you are taking, and what is the error?

That said, I don’t believe the UI for adding package references in VS is up to the new way we handle NuGet packages in EBuild, yet. SO if the issue tis ab out adding a NuGet reference to the library project, can you try doing that in Water instead of VS?

Also, I recon mend updating to the latest .2383, just in case.

[ndelic]

Project attached. Problems:

• It’s not possible to add anything via VS2017 UI (library project reference to UWP project and NetStandard.Library Nuget package to library project).
• I can add all references(library -> UWP, Nuget -> library) by editing the .elements file but then the project doesn’t compile.

I haven’t tried Water because I was under the assumption that it can’t handle UWP projects (I see only WPF template). Just compiling the library doesn’t help me much because I have to be able to debug it (i.e. set breakpoints and step through code) in the IDE. I only use C# UWP project as a shell and have all my cross platform Swift/Silver code in the library.

Unfortunately, I can’t download .2383 because I don’t have beta access.

StraightSync.zip (929.7 KB)

[mh (marc hoffman)]

@ndelic

I haven’t tried Water because I was under the assumption that it can’t handle UWP projects

Correct, it doesn’t support those yet. I meant to try using it purely for adding the reference.

I’ll have a look at your project either later today or tomorrow.

—marc

[ndelic]

Thank you. Btw, I also tried to create a portable library, but couldn’t get beyond this:

[ndelic]

Another thing, if my main project has a shared project reference, NuGet packages won’t install. The installation process starts, everything looks normal, but installation is rolled back at the end. If I temporary remove the shared reference I can install NuGet package without problems. Main project type is Silver WPF.

[mh (marc hoffman)]

@ndelic

• I can add all references(library -> UWP, Nuget -> library) by editing the .elements file but then the project doesn’t compile.

Ok. to the library compiles fine for me here (that’s all thats my area — the UWP and VS-specific issue, someone else needs to take a look at). What Nuget references (name + version) are you trying to add to it, how did you do it when editing the .elements, and how did it fail?

you’’ want something like

<NuGetReference Include="Foo:12.0" />

—marc

[ndelic]

This is what I get in VS2017 output if I try to use the UI to add NetStandard.Library:

Attempting to gather dependency information for package ‘NETStandard.Library.2.0.3’ with respect to project ‘StraightSync.Library’, targeting ‘.NETFramework,Version=v4.0’
Gathering dependency information took 124,7 ms
Attempting to resolve dependencies for package ‘NETStandard.Library.2.0.3’ with DependencyBehavior ‘Lowest’
Resolving dependency information took 0 ms
Resolving actions to install package ‘NETStandard.Library.2.0.3’
Resolved actions to install package ‘NETStandard.Library.2.0.3’
Retrieving package ‘NETStandard.Library 2.0.3’ from ‘nuget.org’.
Install failed. Rolling back…
Package ‘NETStandard.Library.2.0.3’ does not exist in project ‘StraightSync.Library’
Package ‘NETStandard.Library.2.0.3’ does not exist in folder ‘Y:\StraightSync\Client\UWP\packages’
Executing nuget actions took 1,77 sec
Could not install package ‘NETStandard.Library 2.0.3’. You are trying to install this package into a project that targets ‘.NETFramework,Version=v4.0’, but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.

Manually, I do it like this:

<ItemGroup>
    <NuGetReference Include="NetStandard.Library:2.0.3" />
</ItemGroup>

and it actually compiles fine, but afterwards I don’t see any reference to .NET Standard 2.0.3. anywhere in the library in VS UI.

[mh (marc hoffman)]

@ndelic

Manually, I do it like this:

<ItemGroup>
    <NuGetReference Include="NetStandard.Library:2.0.3" />
</ItemGroup>

you dont actually need that reference, as it’ll be added implicitly, but this should work fine, too.

@ndelic

and it actually compiles fine

ok, then what is the problem?

[RemObjectsSoftware (RemObjects)]

Thanks, logged as bugs://82128

[ndelic]

Test project (the one that doesn’t compile) attached. It fails with the following messages:

I manually added NetStandard.Library NuGet reference to library project and library project to UWP project.

StraightSync.UWP.zip (1.2 MB)

[mh (marc hoffman)]

@viktoriad: this seems to be a VS/VC# issue? the Elements project itself compiles fine. We probably need to add the GetPackageOutpits task to the targets file. It seems to be a regular project reference in the VC# project.

    <ProjectReference Include="..\StraightSync.Library\StraightSync.Library.elements">
      <Project>{adc1d1dd-134a-41f7-a7e4-ef8534494eaa}</Project>
      <Name>StraightSync.Library</Name>
    </ProjectReference>

Niko, does this only fail if the VC# project references the Elements one, or also if you open there Elements one on its own? Also, as a workaround, can you use a regular .dll reference instead of a project one, to see if that works? ie:

    <Reference Include="StraightSync.Library">
      <HintPath>..\StraightSync.Library\Bin\Debug\StraightSync.Library.dll</HintPath>
    </ProjectReference>

or whatever the correct path is?

thanx!

[RemObjectsSoftware (RemObjects)]

Thanks, logged as bugs://82129

[ndelic]

1. Elements on Elements works fine, I can add the library project reference to both Elements exe projects via UI and they also compile.

Elements-Elements.zip (1.0 MB)

2. VS lets me add compiled StraightSync.Library.dll to UWP project via UI and it also compiles afterwards.

[mh (marc hoffman)]

Thanx. Seems we need to implement the GetPackageOutputs target int the MSBuild wrapper for EBuild. I’ve logged 82129 for that.

[ndelic]

Elements v2385 change log says this is fixed, but…

[mh (marc hoffman)]

does it?

[ndelic]

This has the same name as my bug report, so I assumed… wrong. I see that the id is actually different from mine.

[mh (marc hoffman)]

Yeah, looks like two issues were logged from this thread; one hand a commit, but both issues are still open.

[ndelic]

Ups, sorry wrong topic.