Don't let the C++/CLI thing fool you: CLI is the C++-y CLI syntax-y issues, it's nothing more than a bridge into .NET.
So the same exceptions you have access to in .NET (i.e. C#, NUnit, etc) are there for NUnit C# test code.
HTH
Best regards,
Michael
--
You received this message because you are subscribed to the Google Groups "NUnit-Discuss" group.
To view this discussion on the web visit https://groups.google.com/d/msg/nunit-discuss/-/_EkKdVMbQ7UJ.
To post to this group, send email to nunit-...@googlegroups.com.
To unsubscribe from this group, send email to nunit-discus...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/nunit-discuss?hl=en.
Don't let the C++/CLI thing fool you: CLI is the C++-y CLI
syntax-y issues, it's nothing more than a bridge into .NET.
So the same exceptions you have access to in .NET (i.e. C#, NUnit, etc) are there for NUnit C# test code.
HTH
Best regards,
Michael
Yessir, this is *one* way to do it. When I've worked with C++/CLI, I like to get away from C++ as fast as possible, at least for reason(s) Charlie mentioned: like lambdas. While you *can* get into some trouble with the C++ language more (differently) than with C#, it's pretty hard to get the CLI *that* wrong that you can't make the leap to test in C#. One thing, you *can* get to IEnumerable extension methods the long way round, but it's much nicer to test at the C# level. There are libraries that help with this, but again, I recommend testing in C# and avoid all that. Anyway, that's my two cent recommendation.
To view this discussion on the web visit https://groups.google.com/d/msg/nunit-discuss/-/Enb3g8URqBYJ.