How can we help you today? How can we help you today?

Initial findings

Seems like a nice and stable product so far (although I haven't had time to use it very much yet) - good work!
Some thoughts:

* Results/All methods pane: add a simple SQL query textbox so I can easily filter/order by my own criteria

* Context menu in VS: move Profiler commands into a subgroup ("folder"), and place it under "breakpoint" or even further below

* using the API when profiler isn't running results in a "Attempted to read or write protected memory" violation. The commands should simply be ignored, or, at least, the error message should be intelligible.

Hopefully, I'll be using it more towards the end of the week - I'll get back to you if I find anything else. Thanks!


And oh, let me know if you want more input on the categorization feature we talked about earlier for upcoming releases!
Jonas Beckeman
0

Comments

3 comments

Sort by
  • richardjm
    In the all methods pane there is a 'filter editor' which may be what you're after. You can get to it by right clicking on the column headings.

    We have moved the addin in the context menu to more or less exactly where you've suggested for release because of the feedback we've recieved. They're now still at the top level but in the same group as 'Run to Cursor'.

    Not sure why you're getting the failure as it should be throwing a ProfilerNotRunningException. We talked about ignoring during design but reasoned that this makes it more obvious that the API is only usable when profiling the application via the main UI. Is this a .NET 1.1 or 2.0 project and if you've got a small test project that shows this error can you zip it up and email it to us at ants@red-gate.com

    Thanks for the feedback.
    richardjm
    0
  • Jonas Beckeman
    richardjm wrote:
    Is this a .NET 1.1 or 2.0 project and if you've got a small test project that shows this error can you zip it up and email it to us at ants@red-gate.com
    Unfortunately it's a pretty huge project. If I try it with a smaller project and it still fails, I'll mail the sln.
    Jonas Beckeman
    0
  • richardjm
    That would be great if you can get it to happen in a smaller project. You're not loading in the Core2.dll directly or anything as we should simply fail to have the dll in the process space catch that exception and rethrow it as a nice ProfilerNotRunningException.
    richardjm
    0

Add comment

Please sign in to leave a comment.