dependency-analyser
dependency-analyser copied to clipboard
drewnoakes
Break dependency upon WinGraphviz
WinGraphviz is great, but it increases the barrier to entry for this tool.
See this question on StackOverflow that details various options.
Original issue reported on code.google.com by drewnoakes on 22 Apr 2011 at 8:55
Maybe the barrier for entry is the lack of an installer? If the GraphViz COM DLL could be embedded and automatically unpacked/used, that could solve the issue... Registration-Free COM Interop - https://msdn.microsoft.com/en-us/library/fh1h056h(v=vs.110).aspx
Another possibility would be bootstrapping the GraphVIZ DLL.
- upload the DLL to the git repository
- add code to download the DLL via cdn.rawgit.com to the machine if it's missing
On second though. This is a bad idea. The DLL is 340 zipped. Adding as an assembly resource and uncompressing/loading should be more than sufficient.
Avoiding separate installation of GraphViz would be great. Can it just be included in the release zip, and picked up from the local directory somehow at runtime, without needing any registry tweaks or other admin-rights-requiring activities.
On 15 October 2015 at 20:28, Jeremy Simmons [email protected] wrote:
Another possibility would be bootstrapping the GraphVIZ DLL.
- upload the DLL to the git repository
- add code to download the DLL via cdn.rawgit.com to the machine if it's missing
On second though. This is a bad idea. The DLL is 340 zipped. Adding as an assembly resource and uncompressing/loading should be more than sufficient.
— Reply to this email directly or view it on GitHub https://github.com/drewnoakes/dependency-analyser/issues/2#issuecomment-148497370 .
Picking up the com registrations is what registry free com is all about. Good set of resources on building the manifest definitions http://stackoverflow.com/questions/465882/generate-manifest-files-for-registration-free-com
Another option is to migrate to WPF and use Graph#.
Graph# looks pretty dead though. There's a port here with one author's modifications:
https://github.com/andypelzer/GraphSharp
an option worth considering for sure!
any downsides?
Sent from my iPhone
On Oct 17, 2015, at 2:44 PM, Drew Noakes [email protected] wrote:
Another option is to migrate to WPF and use Graph#.
— Reply to this email directly or view it on GitHub.