VisualStudioReporter does not work with Visual Studio 2013 about approvaltests.net HOT 5 CLOSED

Can you provide info about the exception?

from approvaltests.net.

Sorry, that's the exception text :)

If you look at VisualStudioReporter.cs, it is hardcoded to vs11 (that is, Visual Studio 2012).

from approvaltests.net.

The third parameter to Registry.GetValue is the default if not found. I've seen seen it launch 2013 on my own machine (unfortunately not the machine I'm using right now). So, it was working a few days ago but I wont be able to test again until this evening.

Maybe that registry key on your machine is still pointing at 2012 for some reason?

Overall the intention is for it to launch in the same isntance of VS that you are already using... so maybe the real issue is to make sure that we know what version we are looking for before we choose the reporter.

from approvaltests.net.

Also, this was fixed in the Nuget release this week, are you on latest version?

Sent from my iPad

On Nov 10, 2013, at 7:37 AM, Jim Counts [email protected] wrote:

The third parameter to Registry.GetValue is the default if not found. I've seen seen it launch 2013 on my own machine (unfortunately not the machine I'm using right now). So, it was working a few days ago but I wont be able to test again until this evening.

Maybe that registry key on your machine is still pointing at 2012 for some reason?

—
Reply to this email directly or view it on GitHub.

from approvaltests.net.

Hi,

I'm using an Azure VM with Visual Studio 2013 preinstalled, running on Windows Server 2012 (from the gallery). I just checked - I did have an older version of ApprovalTests in that solution. After updating to the latest (3.0.5) ApprovalTests, the VisualStudioReporter works!
I still can't manage to get BeyondCompare one working, but I'll open a separate issue for that :)

Thanks, I'm closing this!

from approvaltests.net.