Net standard over net 6.0 about qlnet

[amaggiulli]

will check if I could restore the Multi-targetting, that should solve your issue

[screig]

Thanks

[amaggiulli]

If I enable netstandard 2.0 got troubles in FastActivator class : DynamicMethod ILGenerator and LocalBuilder

[screig]

I did this, changing the TargetFramework and adding the package.

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <VersionPrefix>1.12.0</VersionPrefix>
    <TargetFrameworks>netstandard2.0</TargetFrameworks>
    <LangVersion>latest</LangVersion>
    <DefineConstants>$(DefineConstants);QL_NEGATIVE_RATES</DefineConstants>
    <AssemblyName>QLNet</AssemblyName>
    <PackageId>QLNet</PackageId>
    <PackageVersion>1.12.0</PackageVersion>
    <Authors>Andrea Maggiulli</Authors>
    <Company />
    <Description>A free/open-source library for quantitative finance</Description>
    <Copyright>Copyright (c) 2008-2021 Andrea Maggiulli ([email protected])</Copyright>
    <PackageLicenseUrl>https://github.com/amaggiulli/QLNet/blob/develop/LICENSE</PackageLicenseUrl>
    <PackageProjectUrl>http://github.com/amaggiulli/qlnet</PackageProjectUrl>
    <PackageTags>QLNet QuantLib quantitative finance financial</PackageTags>
    <GeneratePackageOnBuild>False</GeneratePackageOnBuild>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="System.Reflection.Emit.Lightweight" Version="4.7.0" />
  </ItemGroup>


</Project>

Like I said I would have committed this as a branch, but seem to be blocked.

[amaggiulli]

yea that works , have to add back :

<ItemGroup Condition=" '$(TargetFramework)' == 'netstandard2.0' "> <PackageReference Include="System.Reflection.Emit.Lightweight" Version="4.0.1" /> </ItemGroup>

[screig]

Cool

[amaggiulli]

now I have to fight with nuget/github deployement for multi-target 😄 , will ask you to verify once done thanks

[screig]

but why bother with multi deployment, with net standard it can go anywhere, no?

[amaggiulli]

Well, main reason is that I don't want to lose net6.0 optimizations, also I see many open source projects have dropped netstandard in favor of being full dotnet core since it is less limiting in what you can do.
Anyway, as netstandard2.0 is supported (via .net 4.6.2 still being in the live lifecycle), I will restore the multi-target to fix the issue you and maybe others could have.

[screig]

Well that makes sense, and I learnt something, thanks.