Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update versioning assumptions #302

Open
dsyme opened this issue Apr 9, 2019 · 0 comments
Open

Update versioning assumptions #302

dsyme opened this issue Apr 9, 2019 · 0 comments

Comments

@dsyme
Copy link
Contributor

dsyme commented Apr 9, 2019

The TPSDK supports development of TPs for quite antiquated F# tooling.

Going forward we should simplify our life for any future updates to the TPSDK (the current commits will be tagged for older development), e.g. I propose:

  1. Assume TPs are developed using the standard template using .NET Core SDK 2.2+

  2. Assume an F# host tool that is F# 4.5+, using FSharp.Core 4.5.2+ and netcoreapp2.2+ or net461+.

    This corresponds to VS2017 later releases. We could be more aggressive here and say that if you want to deliver TPs for VS2017 you should pin to an specific legacy branch of the TPSDK which we no longer update

  3. Assume reference assembly targets of (netstandard2.0+ or netcoreapp2.0+ or net461+) and FSharp.Core 4.5.2+

We could also move to assume VS2019-era tooling - I believe the main advantage would be assuming any host tooling is at least .NET Framework 4.7.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant