Remotion.Linq.EagerFetching 2.1

25 views
Skip to first unread message

Alexander Zaytsev

unread,
Feb 11, 2017, 10:23:18 PM2/11/17
to re-moti...@googlegroups.com
Hi,

Why there is no EagerFetching v 2.1 on NuGet ?

Best Regards,
Alexander


Michael Ketting

unread,
Feb 12, 2017, 10:39:17 AM2/12/17
to re-motion Users
Hi!

EagerFetching 2.0 shouldn't have any issues with re-linq 2.1. In re-linq there was just the switch to .NET Standard in v2.1 so it's easier to use but the PCL should still work. BTW, with the integration of .NET Core in Msbuild, I hope to be able to integrate .NET Standard into the build without duct tape and chewing gum but I don't have a timeframe.

Best regards, Michael

Alexander Zaytsev

unread,
Mar 15, 2017, 10:36:01 PM3/15/17
to re-moti...@googlegroups.com
Hi Michael,

It turns out that 2.0.1 does not support .NET Standard and so could not be used there. 

Best Regards,
Alexander




--
You received this message because you are subscribed to the Google Groups "re-motion Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to re-motion-users+unsubscribe@googlegroups.com.
To post to this group, send email to re-motion-users@googlegroups.com.
Visit this group at https://groups.google.com/group/re-motion-users.
For more options, visit https://groups.google.com/d/optout.

Michael Ketting

unread,
Mar 16, 2017, 3:35:01 AM3/16/17
to re-motion Users
Hi Alexander!

I've checked with VS2017 and you can set up your project file like this to get it to work (it compiles on my system):
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFramework>netstandard1.4</TargetFramework>
    <PackageTargetFallback Condition=" '$(TargetFramework)' == 'netstandard1.4' ">portable-net451+win8</PackageTargetFallback>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Remotion.Linq" Version="2.1.1" />
    <PackageReference Include="Remotion.Linq.EagerFetching" Version="2.0.1" />
  </ItemGroup>

</Project>

The same does for project.json in VS2015, but with the imports-directive (e.g. in the question http://stackoverflow.com/questions/40676344/adding-framework-imports-to-csproj)

Yes, you have to do this for every project that references the library with the PCL-dependency, which is obviously a pain and the reason Remotion.Linq itself already has a .NET Standard package. As I said, the native build is on the todo list but I don't have a timeframe when to do it and it's possible to do the VS2015 variant first by porting all the .NET Core commits in Remotion.Linq to Remotion.Linq.EagerFetching (i.e. excluding 2861933c32a57f5676dbb990a13416ccfb18fd03 to including 29cd82725117fd43f3fb6966ba76da719e36111d)

Best regards, Michael
Reply all
Reply to author
Forward
0 new messages