I am working on
MyProject which is windows (desktop) application being developed in
C#.NET and DotNet Framework 4 in
WPF. Project is layered as
DataAccessLayer (DAL) -->
BusinessLogicLayer (BLL) -->
This project has a module called
MyModule which needs to be reused in other multiple projects with minimum changes and possibility of bugs.
All projects will be using same development environment as that of
DAL will be entirely different; it will NOT be reused. Module will have no control over it. Module will have
BLL which will be reused by all calling applications. Also UI of module will be modified by calling application.
XAML code will not be a part of distribution; it will be newly written by calling application.
This module will be provided to other projects in form of compiled DLLs. Calling application will write its own
XAML code and will bind
ViewModels exposed by module. Ideally that should work but little extra may be needed.
Additionally, BLL will be distributed which will be reused as is.
This module consists of one main UI window. From this main window, multiple sub windows will be launched. Module raises events those needs to be handled by calling application. Module needs inputs those needs to be provided by calling application.
Microsoft decides (I am sure they must be doing it now) to reuse "Options" window (File-Options) across all MS Office projects. But each project can decide GUI of window, where the settings should be saved, how (XML/INI file etc.) the settings should be saved etc.
I am planning to expose one
ViewModel per window. I will also expose events/enums/structs as necessary. To accept data (as
DAL will be entirely different), I will expose
DTO classes which calling application will inject in module.
I have created reusable modules earlier many times. All those modules were DLLs without GUI. There was no role of binding UI elements and events with calling application, allowing caller to design its own UI etc. My key problem here is how to achieve this? What guidelines should be followed? What architecture should be used? How to expose an interface in a
DLL that is bindable to a
You may suggest corrections in my plan or discard my plan all away and suggest your new plan.
DLLthat is bindable to a
WPFproject? I have edited the question.