Hi,
We have created an extensive api system and data structure using interfaces and DI. To access data, if the application is a Windows / WCF service, then the LINQ repository implementation is introduced at runtime using Castle. The / winform client web applications use the same data controllers / domain objects, but parts of the implementation use the introduced WCF client classes to access the data. The great part of this setup is that the client and server code can reuse the same domain objects, services, and system logic by including the appropriate assembly with multiple translations.
I just created a Silverlight application using the "Silverlight Navigation Application" template in VS2010. It seems the only way I can reference my working CLR code is to link classes (add an existing / linked element). There is no load on the boat plumbing classes, but there are some basic classes that handle routing interfaces for emails, SMS messages, logging and data access using lock micronucleus files and application configuration files.
I can display grids and more by linking controls to WCF service links. However, I would like to reuse the controller model for messaging, data access, logging, and so on. I can’t determine if it’s worth trying to fit all existing classes into SL project classes or start thinking about somehow creating a new lightweight api for SL? Has anyone had experience with unity / castle and Silverlight?
source
share