Merged
Conversation
Contributor
Author
|
During the regular rebuilding and running tests to see whether I did not destroy anything I found an additional issue with the testing method Basically there is a small percentage that this test fails, it is probably due to the usage of the |
Owner
|
@Tycjan-Fortuna-IT looks good. I am accepting the pr. Many thanks for your contribution. |
This file contains hidden or 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
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.
The first commit is related to the issue #416.
I've updated NuGet packages to latest stable versions and unified dependencies across projects. Here is a table of updated packages with the corresponding package name and its old and new version.
Additionally the version of package⚠️ , which I also did update to the long term support one.
Microsoft.ApplicationInsightswas deprecatedI additionally, resolved inconsistencies by unifying package versions across different projects within the
ExDataManagementsolution.The second commit is related to the issue #415.
I did add the prefix TP.ExDM to all namespaces inside the
ExDataManagementsolution.After making changes, the unit tests were used and the tests passed 🟢.