Glenn Block

Actively enforce your conventions

It's good to be loved.

Some thoughts:

Assembly.ReflectionOnlyLoad is likely better than Assembly.Load unless the assemblies you're checking are also references in your test project.  You might get false test failures if all the dependant assemblies aren't in the same directory.

If they are references in your test project (which means all their references are also copied to the same directory) then I'd recommend using a type from each of the assemblies instead of a "magic" string.

For example:

var asms = new Assembly[]

                  {typeof (Prism.Interfaces.IRegionManagerService).Assembly,

typeof (Prism.RegionManager).Assembly};

..this way you get compile-time errors should the namespace names change (which would be runtime errors using strings).

You've been kicked (a good thing) - Trackback from DotNetKicks.com

Wouldn't be more easy to use a NDepend/CQL rule, in your case it would look like:

WARN IF Count > 0 IN SELECT ASSEMBLIES WHERE

IsDirectlyUsedBy "ASSEMBLY:Prism.Interfaces" AND // ASSEMBLY: is here to avoid conflict with namespaces

NameLike "Unity"  // Or any regex

Also with System.Reflexion you expose yourself with plenty of problems I ran throught the past years:

codebetter.com/.../mono-cecil-vs-system-reflection.aspx

@Patrick this is a greate idea.

@Chris

Unity is loved by the Prism team! It's the container we're shipping with on our RI. I think we're one of Unity's first customers :)  

We want to make it easier for those that prefer other containers and therefore want to remove hard dependencies in the core.

Pingback from  Reflective Perspective - Chris Alcock  » The Morning Brew #87

Recently, both Glenn Block and Ayende wrote about how to define some sort of active conventions about

Recently, both Glenn Block and Ayende wrote about how to define some sort of active conventions about