Thanks for the replay. Not sure that example really hits home.
Here are 2 different examples:
In Example1 youll see where I was trying to have a project of just user controls and access one of those controls in a different module within a view.
In Example2 youll see where I made the 'Usercontrol' project, a module, copied it to the Modules directory (Bin\Modules), and then created a dependcy
in the ModuleA
As im thinking about this I may be going about all this the wrong way. Maybe instead of creating an assembly of nothing but usercontrols I should just create modules with
Views that display what I want. If i need to use this view then I'll load it and place it on the screen.
The way I was approaching it was that a Module can have 1 or many Views and a View can contain 1 or many usercontrols. That being said there may be several Modules(Views)
that can use the same usercontrol, so I was going to create a project of all the common usercontrols and then use them in the views where I needed them. But with
the Dynamic Modularity approach it appears the Modules are being loaded before the Usercontrol assembly is being loaded, thus I get an error.
Hope that helps explain it a bit more.