tag:blogger.com,1999:blog-10748614.post116133894887897445..comments2024-02-28T12:34:09.691-05:00Comments on FrazzledDad: Testing Helper MethodsJim Holmeshttp://www.blogger.com/profile/05869146736565695900noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-10748614.post-1161560622656034362006-10-22T19:43:00.000-04:002006-10-22T19:43:00.000-04:00One way I've been doing this is to use the new Int...One way I've been doing this is to use the new InternalsVisibleTo attribute in .Net 2.0. I stumbled across this when I was doing my (very painful) strong naming of Enterprise Library. Basically all you need to do is have the methods you want to expose for testing (but not publicly) be marked internal rather than private. Then, in the assembly file of the project you are testing you can add the assembly: InternalsVisibleTo. You feed it the testing assembly name. You can strong name to add more security around this (but be aware that they want the full public key for the attribute, not the public token which is much easier to type).Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-10748614.post-1161400256784537032006-10-20T23:10:00.000-04:002006-10-20T23:10:00.000-04:00Veerrrrry clever, Jim.Interesting.Veerrrrry clever, Jim.<BR/><BR/>Interesting.Anonymousnoreply@blogger.com