Closed Thorium closed 2 years ago
The answer seems to be yes, you can update the dll, but then your TypeProvider won't work anymore.
We should fix this - my understanding is that adding a netstandard.dll
to your TPDTC will basically no longer be needed
Are you using a separated TPDTC like we discussed at F# Exchange?
I didn't get the CompilerServices.TypeProviderAssembly in the TPRTC to find the given TPDTC (as they are in different runtimes and paths?) and also the LemonadeProvider example referenced explicitly the old TPDTC netstandard.dll in LemonadeProvider.DesignTime.fsproj:
<None Include="..\..\packages\NETStandard.Library.NETFramework\build\net461\lib\netstandard.dll" Condition="'$(TargetFramework)' == 'net45'">
<CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
</None>
It seemed also that the source code is about the same files for both, so I went to the easy road and reverted back the old version of netstandard.dll, and suddenly everything worked fine.
This has been removed a while back
The Readme.md tells the user reference to
NETStandard.Library.NETFramework
at Making a .NET Standard 2.0 TPDTC. This also comes with the LemonadeProvider template.However, NuGet package of NETStandard.Library.NETFramework contains only non-stable version available, and the package states:
So my question is that should I rather include a netstandard.dll from my installed frameworks
C:\Program Files\dotnet\sdk\
to the NuGet package, and which version? At least2.1.202\Microsoft\Microsoft.NET.Build.Extensions\net461\lib\
seems to work?