Migrate QuickGraph to QuikGraph and GraphSharp to GraphShape. #17
Conversation
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
|
Awesome! |
Author
|
Just an update to use latest libraries versions with strong names. |
Contributor
|
@KeRNeLith Thanks for this! I'm not a maintainer anymore, so I've included your changes in my PR for the .NET Core migration. |
Author
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Hello,
I updated the quite old QuickGraph and GraphSharp dependencies to respectively QuikGraph and GraphShape.
Those libraries are using modern C# development workflow, have been ported to .NET Core with a wider support in term of targets.
And finally they come with a huge set of unit tests that has helped to debug and fix a lot of issues in both libraries.
Since they have been built using recent toolchain they will certainly help you to port your app to .NET Core (I faced issue with the old version of those libraries while tying to use the Microsoft.NET.Sdk.WindowsDesktop for WPF applications). Those reworked libraries allow to get rid of such issues.
Here are the links to both libraries: