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

Enable selection of latest SDK #26

Closed
idg10 opened this issue Jun 12, 2020 · 0 comments · Fixed by #27
Closed

Enable selection of latest SDK #26

idg10 opened this issue Jun 12, 2020 · 0 comments · Fixed by #27
Assignees

Comments

@idg10
Copy link
Contributor

idg10 commented Jun 12, 2020

Because of #22 we currently target .NET Core SDK 3.1.102.

Even though the SpecFlow issue that drove this SpecFlowOSS/SpecFlow#1912 is marked as closed, at the time of writing, this fix is still only in preview builds of SpecFlow. (It's fixed in 3.3.)

However, it's hard to test whether we still have this problem without modifying these templates, at which point we risk breaking everything again.

So it seems to make sense to introduce some sort of option for controlling the SDK version.

In the long run, we want to put the default SDK back to 3.x, so it would be useful to have a way to opt in to using a specific version when necessary. For now, we want a way to opt into using 3.x so we can test ahead of imposing it on everyone

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