Comments

For me, production profiling is easily the killer feature that we've been waiting for.

Better support for remote profiling would be great too..especially if it could be done via. a hosted silverlight application, eliminating the need to have the profiler installed locally and to send all of the profiling information over the wire (not sure about the feasibility of that, though).

But something around remote debugging would be great, but locked down to a specific IP or something. So I can only see querying done for the requests I'm making, and it doesn't capture anything else.

I think the interface for showing query plans needs an overhaul, I still use SQL Server Management Studio for looking at query plans because it just feels too clunky in NHProf.

Also something to exclude sessions from certain URL's, for some web pages with AJAX requests I end up with a few sessions when all I want to profile is the initial page load or a single AJAX request.

Otherwise, I've gone from hating NHProf because it was expensive program that didn't justify it's cost (in my opinion) when initially released. To a bloody useful program that I now use on a daily basis. :)

What I would love to see is a generic DB connection handler to support all the Micro-ORM's out there. I know that it won't be as un-obtrusive as the current profiler support, but it would be great new product line that I would buy.

The ability to execute ad-hoc queries. I want to be able to type in a query using HQL, Criteria, or QueryOver, and have NHProf execute and profile it.

Improve the layout of insert statements, it's difficult to match up parameters and values.

The ability to display the statement issued to the server instead of the parsed SQL. With SQL Server, there may be a vast performance difference between the parsed SQL as shown in NHProf and the SQL wrapped in sp_executesql that is actually sent to the server.

Jamie,
* You might want to look at NHibernate Query Analyzer. What you request is something that we aren't likely to support inside the profiler.
* I would like to see what you mean by improving insert layout.
* As for the last one, we aren't likely to support it, it requires a LOT of information about the actual DB engine, and at that level, you are probably better off using the database own mechanisms, rather than a higher level tool like the profiler