This question was closed May 07, 2013 at 12:05 AM by Julien-Lynge for the following reason:

Feedback request

Question by eventropy · May 06, 2013 at 08:54 PM · assemblies error-handling external-tools

Double Clicking Errors/Output In The Console Triggered By External Assemblies

I've moved a lot of my code to an external assembly. That is, I'm compiling my code as a class library in visual studio to DLL files, w$$anonymous$$ch are placed in the Assets/ directory. T$$anonymous$$s works well but one t$$anonymous$$ng that I really miss is the ability to double click errors or logging information in the console view and jump directly to the source file that triggered it. T$$anonymous$$s works fine when the script is in the Assets/ directory but does not$$anonymous$$ng in the case where it links into an assembly.

In the case of errors like NullReferenceException, it even prints out the exact path to the file and line number, yet unity does not open it. Even if there was a way to open it in script myself by catc$$anonymous$$ng the double click, that would work as well.

0 Show 1

Julien-Lynge · May 07, 2013 at 12:05 AM 0

This sounds more like a feedback request than a question for the community - I suggest putting it on the feedback site and then linking to it from here. You're also welcome to discuss it on the forums, but again, unless you have a specific question UA isn't the right place for this discussion.