Thanks guys Tim certainly is right about not hitting the disk, but I've got another idea to avoid it - a method that would get the object on runtime, examine it by reflection and return the code to create a mock of it, ready to paste to the unit test - including the data insertion. Are there such things in this world?
greets hp --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino.Mocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/RhinoMocks?hl=en -~----------~----~----~----~------~----~------~--~---
