Featured post
.net - Tips/Resources on Structuring Shared Code Libraries in C#/WPF? -
i've written simple desktop application c#/wpf , i'm looking create another, larger application share of functionality. i'm thinking should create 3 separate projects: 1 containing shared code, , 1 each 2 apps.
my problem i'm not entirely familiar .net/wpf don't know if there best practices sort of thing. can offer sources of information, example projects or brief advice?
edit: put little more detail on scenario, first application specialised editor , second application taking file editor , wrapping project model around create sort of basic ide.
honestly depends on level code intend share is. instance, it's entirely plausable put of business logic code 1 project/class library , maintain independantly, mixing biz logic wpf custom controls should discouraged. think layers of abstraction modularizing, , dependancy heiarchy introducing , refactor accordingly.
edit:
in response above changes suggest following: logic , dal associated above should pushed project seperate namespaces. visual elements (the view, viewmodel) should moved seperate project , namespace set well. once can merge these , launch them exe contains host window , usercontrol rest of hosted visual content, can move forward integration larger ide project. key here is:
visual layer , view logic -> editor.visual.dll
biz logic & data access -> editor.core.dll
i hope helps.
- Get link
- X
- Other Apps
Comments
Post a Comment