Nikolay,

We are targeting multiple platforms this way.
Our lowest supported .NET version is 4.0, that's what Apache.Ignite.sln is
for, and all the related projects.
However, .NET 4.0 is old and not cross-platform, so we also target .NET
Core 2.0.

We have to have separate solution and project files for that
(Apache.Ignite.DotNetCore.sln) for multiple reasons:
* Normally you can multitarget as part of one csproj file, but not with
with a combination of .NET 4.0 and .NET Core 2.0
* There are legacy integrations (ASP.NET, EF) that do not compile under
.NET Core.

This is going to change in Ignite 3.0, we will get rid of the legacy parts
and move on to .NET Standard 2.0.

Thanks,
Pavel

On Wed, Apr 1, 2020 at 1:08 PM Ilya Kasnacheev <ilya.kasnach...@gmail.com>
wrote:

> Hello!
>
> As far as my understanding goes, v4.0 is for .Net classic, such as Mono.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 1 апр. 2020 г. в 13:04, Nikolay Izhikov <nizhi...@apache.org>:
>
> > Hello. Igniters.
> >
> > I working on some issue in .Net platforms and found that different
> project
> > files for .Net contains different platform versions.
> > Can someone explain why?
> >
> > 1. Apache.Ignite.Core.csproj [1]
> >
> > ```
> > <PropertyGroup>
> > ...
> >   <TargetFrameworkVersion>v4.0</TargetFrameworkVersion>
> > ...
> > </PropertyGroup>
> > ```
> >
> > 2. Apache.Ignite.Core.DotNetCore.csproj
> >
> > ```
> > <Project Sdk="Microsoft.NET.Sdk»>
> > …
> >     <TargetFramework>netcoreapp2.0</TargetFramework>
> > …
> > </Project>
> > ```
> >
> >
> >
> >
>

Reply via email to