Closed GoogleCodeExporter closed 9 years ago
Thanks for your bug report.
Unfortunately I cannot reproduce this issue on my machine. Furthermore I am
also running Win7 Pro on 64-bit.
Are you sure that you have installed WinGraphviz? If so, what version is
installed? Unfortunately the Dependency Analyser takes a dependency on a COM
DLL which must be installed before it can run. Could you try re-installing it
anyway? An MSI installer is included in the download.
Maybe a good idea would be to detect when WinGraphviz is not installed and
report an appropriate error message. If you could let me know whether this
fixes the problem, perhaps I can use this information to add such a feature.
Original comment by drewnoakes
on 24 May 2011 at 4:24
Yes, I installed WinGraphviz using the MSI prior to running Dependency Analyser.
The problem was due to the UAC. It works ok if I run the Dependency Analyser as
an admin.
This did not resolve the problem I had opening a VS2008 SLN file, noted in
another issue.
Original comment by dhoc...@gmail.com
on 24 May 2011 at 4:31
Hmm that is strange. I don't believe I have to run with elevated permissions.
I'll do some more tests.
The other issue is a known limitation of the app that should be easy to fix but
I don't have much bandwidth now. If you fancy giving it a shot, great.
Long term I'd like to remove the dependency on WinGraphviz for a .NET solution.
It'd simplify installation and allow execution on other platforms via Mono.
Original comment by drewnoakes
on 24 May 2011 at 4:38
Sounds good. Thanks for your help and for a making a useful tool for free. I
may try to take a stab at updating it if I can get a bit of free time.
Original comment by dhoc...@gmail.com
on 24 May 2011 at 4:53
Hi had the same issue as dhoc, could get it to work with elavated privileges.
Original comment by gbminn...@gmail.com
on 4 Nov 2012 at 2:07
I believe 47335c38fb1cd9f99582104732b67e0181488b8c fixes this issue. The http://wingraphviz.sourceforge.net/wingraphviz/ ver1.02.25s we built against is a 32-bit COM DLL. Targeting x86 handles this automatically.
@jeremysimmons I take it you're referring to this line in particular:
Feel free to close this if you think it's solved.
Yes that's exactly it. Must target x86 so the com dll loads.
Original issue reported on code.google.com by
dhoc...@gmail.com
on 24 May 2011 at 3:22