13

[okay to merge now] - move to .NET Standard exclusively by cartermp · Pull Reque...

 4 years ago
source link: https://github.com/fsprojects/FSharp.TypeProviders.SDK/pull/339
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

Contributor

cartermp commented on Apr 11 •

edited
  • Remove .NET Framework and Mono pieces of this repo
  • Adjust guidance so that we don't injure people with the "type provider that tries to also support older .NET Framework and .NET Standard and .NET Core and older Visual Studio" confuse-o-tron
  • Use paket consistently throughout the repo
  • Move TPDSDK to a proper project that can be published to NuGet
  • Remove more vestiges of non-.NET Standard assembly nonsense in testing and update all skipped tests appropriately
  • Update template
  • Solve the template generating some broke ass old paket.lock for some reason
  • Figure out why Provided Namespaces don't show in the BasicProvider unit test via project reference
  • Fix factoring of leaking implementation details for tests (namely the caching stuff)
  • Figure out stack overflow in tests
  • Do more targeted README updates to try and make it as simple as possible
  • Manually verify all examples

This simplifies the repo and how Type Providers build moving forward. The downside is that older .NET Framework and older F# consumers won't be able to use newer type providers build with the SDK in this state. That is also largely true today, though, as many type providers are updated and do not support these older environments.


report

Recommend

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK