Update to latest TestCentric.Engine dev release #1159
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Good work. Sorry about the version issue. I normally manage the dev builds manually, deleting any are too early. But looking at the dates is the simplest way to be sure. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR closes #1144 by updating the project reference of the TestCentric.Engine.
The details about the actual fix can be found in the PR 213 to that project.
When using the latest version of the TestCentric.Engine, the Stop and Kill button works reliably. The behavior was checked using the hung-tests.dll for different .Net framework versions (4.62, Core 3.1, .Net 7.0...)
As this was my first time updating a project referecence, I was a little surprised at the version number of the dev releases. I initially thought that the highest number will be the latest dev release. But I notice that it's different here by checking the release dates. So I finally chose the version 2.0.0-dev00008. Is there any smart approach to detect the latest dev release differently?