improve installation section #2058
Conversation
SabotageAndi
force-pushed
the
docs/ImproveInstallationSection
branch
from
50773d7
to
87fdfb9
Compare
| @@ -3,7 +3,7 @@ | |||
| ## General | |||
|
|
|||
| You need to use the MSBuild code behind file generation for SpecFlow 3.0. | |||
| Version after SpecFlow 3.3.30 don't need to add the `SpecFlow.Tools.MSBuild.Generation` package anymore to your project, if you are using the `SpecFlow.NUnit`, `SpecFlow.MSTest`, `SpecFlow.xUnit` or `SpecRun.SpecFlow.3-3-0` package. | |||
| After version SpecFlow 3.3.30 don't need to add the `SpecFlow.Tools.MSBuild.Generation` package anymore to your project, if you are using the `SpecFlow.NUnit`, `SpecFlow.MSTest`, `SpecFlow.xUnit` or `SpecRun.SpecFlow.3-3-0` package. | |||
There was a problem hiding this comment.
For some reason there is no space or line break between the two sentences
There was a problem hiding this comment.
That's strange. Locally the linebreak was there.
| @@ -3,7 +3,7 @@ | |||
| ## General | |||
|
|
|||
| You need to use the MSBuild code behind file generation for SpecFlow 3.0. | |||
| Version after SpecFlow 3.3.30 don't need to add the `SpecFlow.Tools.MSBuild.Generation` package anymore to your project, if you are using the `SpecFlow.NUnit`, `SpecFlow.MSTest`, `SpecFlow.xUnit` or `SpecRun.SpecFlow.3-3-0` package. | |||
| After version SpecFlow 3.3.30 don't need to add the `SpecFlow.Tools.MSBuild.Generation` package anymore to your project, if you are using the `SpecFlow.NUnit`, `SpecFlow.MSTest`, `SpecFlow.xUnit` or `SpecRun.SpecFlow.3-3-0` package. | |||
There was a problem hiding this comment.
Suggestion for the second sentence:
Starting with SpecFlow 3.3.30 you don't need to add the "SpecFlow.Tools.MSBuild.Generation package manually to your project, because it is automatically installed with the selected unit test provider package as dependency.
There was a problem hiding this comment.
It would be nice to link the "unit test provider package" to the details of it (to spare the list and the warning that you need only one of them, etc.), but I did not find a heading/section that we could easily link yet.
There was a problem hiding this comment.
I made a link to the unit test providers page
Types of changes
Checklist: