NI Measurement Studio Idea Exchange

About NI Measurement Studio Idea Exchange

Have a new Idea for MStudio?

  1. Browse by label or search in the Measurement Studio Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click New Idea to submit a product idea to the Measurement Studio Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
cancel
Showing results for 
Search instead for 
Did you mean: 

Provide better debugging information in .NET exceptions

The information provided with exceptions has not been useful in determining the problem cause.  For example, the latest bug I've been dealing with in my code involves 2 tasks trying to access the same resource.  The exception gives the name of the task that throws the exception.  Great.  It's really easy to tell which task throws the exception because, well, it's throwing the exception.  What the exception message doesn't tell me are the other task(s) that have that resource.  The really useful information is consistently lacking in exception messages.