This question is locked. New answers and comments are not allowed.
Hi guys,
Could u pls explain me how solution should be structured if solution is using modular architecture...
So there is main Shell project which just shows Modules in regions (for example prism).
Some Module projects use telerik libs (some use grids, some other components, etc..some use different version) via references to dll....
I don't add telerik lib references into main shell project, as it should not know anything abt module dependencies.
Problem is when solution starts. Main shell project complains that telerik libs missed, 'http://schemas.telerik.com/2008/xaml/presentation' is an unknown namespace, types not found, module is not registered, etc.. etc...
The only way is to add references to telerik libs into main Shell app - then everything is OK....
But Shell should NOT know abt this.. so it should not reference module dependencies libs....
??????
Could u pls explain me how solution should be structured if solution is using modular architecture...
So there is main Shell project which just shows Modules in regions (for example prism).
Some Module projects use telerik libs (some use grids, some other components, etc..some use different version) via references to dll....
I don't add telerik lib references into main shell project, as it should not know anything abt module dependencies.
Problem is when solution starts. Main shell project complains that telerik libs missed, 'http://schemas.telerik.com/2008/xaml/presentation' is an unknown namespace, types not found, module is not registered, etc.. etc...
The only way is to add references to telerik libs into main Shell app - then everything is OK....
But Shell should NOT know abt this.. so it should not reference module dependencies libs....
??????
2 Answers, 1 is accepted
0
Accepted
Hello Vit100,
Vlad
the Telerik team
Why you need our URI namespace in your main project if you do not use our components there?
All the best,Vlad
the Telerik team
0
Vit100
Top achievements
Rank 1
Rank 1
answered on 21 Mar 2011, 03:14 PM
Never mind.. my mistake
in moduleCatalog.xaml i had wrong name for Ref parameter....
in moduleCatalog.xaml i had wrong name for Ref parameter....