Doesn't seem to work in Visual Studio 2012 express - Exception Options? about fsharpkoans HOT 8 CLOSED

actually, this frustration runs so deep that I have re-implemented the AssertThrows helper:

let AssertThrows<'a when 'a :> exn> action = try action() with e -> Assert.IsInstanceOf<'a>(e)

doing so ensures that the closure is run inside "user code". I'm not necessarily suggesting that this change be made here, but at least wanted to share this as an option for others.

from fsharpkoans.

Yeah, I ran into this problem once before during a workshop with the koans. I don't think we found a good workaround for it at the time, but doing some googling, it appears that this may be a workaround.

http://msdn.microsoft.com/en-us/library/038tzxdw.aspx

I can't verify that it works right now, but if it does, I'm happy to update the readme with the info.

from fsharpkoans.

Another approach would be to Start without Debugging (Ctrl + F5).

from fsharpkoans.

Hi, I was the guy who couldn't get it to work, I just can't seem to find that Debug -> Exceptions thing even in Expert Settings Mode.

from fsharpkoans.

If I remember correctly, they removed the ability to filter exception types in the express editions (starting with VS 2012). See this for possible fixes if that isn't the case.

You can also navigate to the application output directory (ex. FSharpKoans/bin/Debug) and run FSharpKoans.exe outside of Visual Studio.

from fsharpkoans.

Closing as this is just the way things work, see above for how to change your exception settings

from fsharpkoans.

this is so unsatisfactory !!! ugh

just so others can see, the most current fix is to uncheck "Enable Just My Code" in Debugging options, but this is a global setting and is usually only recommended to turn off when debugging your dependencies. also, similarly to running without debugging, it doesn't break on __ "holes", requiring you to read the console output to find the error. altogether nonideal.

i know this is a problem with NUnit's interaction with Visual Studio, not with this repo, so excuse my frustration.

from fsharpkoans.

Sorry about that. As you said, this is just a result of the way the NUnit exception handling works with VS, so there isn't much that we can do. Hopefully you still learn something from the koans despite the inconvenience of referencing the console output. :-)

from fsharpkoans.