471,350 Members | 1,943 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,350 software developers and data experts.

InternalsVisibleTo chicken and egg problem?

Hi all,

I'm trying to create unit tests in a seperate assembly from the
library. However there are some internal classes that deserve testing
but are not intended to be used by the public.

I'm trying to use the InternalsVisibleTo attribute so that the unit
test assembly can see the internals of the library for testing. The
unit testing is done a release version which is given a strong name
(the unit test assembly gets a strong name as well). The problem is
that the attribtute, when used with a PublicKeyToken attempts to verify
that the unit test assembly exists, which it doesn't, because it
depends on the library assembly.

The result is that the library is built with warnings, and the unit
test assembly can't see the internals..

any ideas on getting around this?


Feb 22 '06 #1
0 1297

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

6 posts views Thread by Mary Ellen Curtin | last post: by
9 posts views Thread by gzinger | last post: by
5 posts views Thread by Petrakid | last post: by
reply views Thread by XIAOLAOHU | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.