http://elegantcode.com/2009/01/12/reflection-helper-for-dto-testing/?utm_source=rss&utm_medium=rss&utm_campaign=reflection-helper-for-dto-testing Sun, 12 Feb 2012 18:54:00 +0000 hourly 1 http://wordpress.org/?v=3.0.5 http://elegantcode.com/2009/01/12/reflection-helper-for-dto-testing/comment-page-1/#comment-42795 Chris Tue, 13 Jan 2009 06:14:35 +0000 http://elegantcode.com/2009/01/12/reflection-helper-for-dto-testing/#comment-42795 Oh, and don't forget this guy in your AssemblyInfo.cs in the project containing the DTOs, [assembly: InternalsVisibleTo("YourTestAssembly")] Oh, and don’t forget this guy in your AssemblyInfo.cs in the project containing the DTOs,
[assembly: InternalsVisibleTo("YourTestAssembly")]

]]> http://elegantcode.com/2009/01/12/reflection-helper-for-dto-testing/comment-page-1/#comment-42794 Chris Tue, 13 Jan 2009 06:11:58 +0000 http://elegantcode.com/2009/01/12/reflection-helper-for-dto-testing/#comment-42794 I prefer a reflection-less approach for testing internals. In your example you would create a class in your test project that inherits from whatever class has the protected internal member. In that class you can add a ctor that takes an expected create date, set the protected internal member which you now have access to, and voila, test your internals without reflection. I prefer a reflection-less approach for testing internals. In your example you would create a class in your test project that inherits from whatever class has the protected internal member. In that class you can add a ctor that takes an expected create date, set the protected internal member which you now have access to, and voila, test your internals without reflection.

]]>