Joseph Musser

My feedback

  1. 22 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    Joseph Musser supported this idea  · 
  2. 30 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    Joseph Musser supported this idea  · 
  3. 21 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    Joseph Musser supported this idea  · 
  4. 2 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    Joseph Musser commented  · 

    This could only happen if 1) NCrunch moved to AOT compilation on Mono and ran your tests in Mono instead of the CLR or 2) Microsoft begins supporting .NET Core running on ARM and NCrunch moves to .NET Core.

  5. 2 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    Joseph Musser supported this idea  · 
    Joseph Musser commented  · 

    That was fast! Thanks!

    I appreciate the speed but unfortunately it is not usable yet. The message is not formatted and AggregateException is not unwrapped as I had asked. There isn't much room for the column. I want to see `Assert.AreEqual failed. Expected:<1>. Actual:<2>.` That will barely fit in the window already, but there's no way I'm going to see it when the column actually contains: `System.AggregateException: One or more errors occurred. ---> Microsoft.VisualStudio.TestTools.UnitTesting.AssertFailedException: Assert.AreEqual failed. Expected:<1>. Actual:<2>.`

    Currently, I only have enough room for it to show `System.AggregateException: One or more erro...`.

    I am never going to want to see AggregateException. If someday it matters, the fact that the exception was wrapped in an AggregateException is something I can see from the results pane when I click on it.

    For the column, please find the innermost exception, put its Message property first, followed by the short name of the type (.GetType().Name).

    Joseph Musser shared this idea  · 
  6. 57 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    Joseph Musser supported this idea  · 

Feedback and Knowledge Base