This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I have a Prism module that is discovered at run-time through directory scanning. When I try to discover a module that uses the Chart component, it fails unless I have the chart reference included in the main control. I don't want to do this, because as I release additional Prism modules that should be used as discovered, I don't want to change my main application. |
|
|
Hello It is a bit tricky for us to reproduce this from scratch, could you please send us a repro project that demonstrates failing to discover a module that uses the chart component? Jason Fauchelle |
|
|
Hi Jason! I just discovered the issue today and it was simply the module is using Mindscape assemblies where there are not used anywhere else in the main project. So since the main project can discover the prism module, it can find the Prism module dependencies and fails. So sorry about the wild goose chase! |
|
|
No problem at all, great to hear you resolved the problem. Jason Fauchelle |
|