Update doc for FailPrivateFieldCalledInNestedClassAspectAttribute.
introduce new test class which exposes a scenario where testeroids should be able to simplify triangulation.
Introduce TriangulationValuesAttribute
add temporary NUnitDependencies_Todo_Create_NuGet folder to hold dependencies for Nunit hich have not yet a proper NuGet package.
add dll references for NUnit dependencies : replace this with a proper NuGet package
introduce TriangulatedFixture and TriangulatedTestMethod to  wrap our tests. right now, tests are inconclusive and never even run...
attempt at structuring the triangulation of values
Merge remote-tracking branch 'origin/master' into Triangulation_Engine
Getting closer !

then_operand2_matches_minus7 is green, but should have a red counterpart induced by the triangulation. inverting the logic of the assertion shows a red test without detail : clearly the problem is that the test runner misses an entry : maybe a resharper-related issue ?
Tests show up correctly in VS2012 with the NUnit test runner adapter now.

http://nunit.org/index.php?p=vsTestAdapter&r=2.6.2
Test name is changed to reflect the triangulated values used !
commented out test that is expected to fail.
Give it a shot with this.Parent being populated to try and support NCrunch

(see http://forum.ncrunch.net/yaf_postsm3921_Support-for-NUnit-s-ISolutionBuilder-and-TestSuite.aspx#post3921)
Give it a shot with this.Parent being populated to try and support NCrunch

(see http://forum.ncrunch.net/yaf_postsm3921_Support-for-NUnit-s-ISolutionBuilder-and-TestSuite.aspx#post3921)
add .pfx file
Merge remote-tracking branch 'upstream/master'
For triangulation purposes abstract classes can be marked with TestFixtureAttribute for that case it's not needed contain a method with test attribute
Removed AbstractTestFixture and need to mark things TestFixture
Removed TestFixture to distinguish between testeroids and other classes
Add GC.SuppressFinalize(this.Sut) to the ContextSpecificationBase.
Update code cleanup settings.