We are mocking an interface which includes an int property with both get and set accessors:
int MaxParasToScan
{
get;
set;
}
In most cases, nMock's ClassGenerator.Generate() produces correct code, a single MaxParasToScan property with both a getter and a setter. But in some environments, it generates code as in the file BadMockIVwRootBox.cs, which I will attempt to attach...
2008-12-22 20:00:45 UTC in NMock