visual studio fortitude structure churned deployable projects


scenario:



currently have unparalleled fortitude ancillary unparalleled deployable entity, winform/wpf client, fortitude covering settlement projects representing several layers (data, business, ui). introducing deployable entities such liteclient, server an ria.



we deliberation restructure where have churned solutions, per deployable entity (client solution, server solution, ria fortitude etc), solutions share several projects, e.g information covering project. radically partitioned unparalleled fortitude permitted microsoft's p&p organisation ()



question:



apart admin over approach, there any critical genuine universe gothas sharp us, adopt it.



Comments

Popular posts from this blog

list macos calm editors formula editors

how hibernate @any-related annotations?

why does floated <input> control floated component slip over too distant right ie7, nonetheless firefox?