i hope not obscure question. expect there several ways people accomplish , approach i'm using seems excessively labor-intensive.
how break apart presentation-layer project (xaml/wpf) several temporary "side-by-side" projects can make enhancements efficiently in vs 2015 , unit-test them quickly? end result being that, once unit tests successful, combine projects again (with focus on organization rather developer efficiency).
the problem me not 1 of analyzing inter-dependencies, not 1 of identifying project boundaries, , not 1 of adding newly created (temporary) project references needed. biggest problem have silly xaml namespace references (clr-namespace:). need updating point new home assemblies (assembly=) referenced resources. ton of overhead , doesn't have pay-off since temporary work in first place. tool me? , revert out afterwards don't accidentally promote temporary xaml changes source control?
i thought managing entirely separate set of sln's , csproj's wip development impossible same underlying reason based on way xaml namespace references (clr-namespace:) work. hard team effort.
more info:
the reason ask because have number of projects xaml resources (user controls, resource dictionaries, etc). of these quite large because organized in way makes them common place put stuff (ie. combobox lookup - alt-down - windows, or common data templates, or what-not). on time becomes problem because vs build operations take long (impacts development efficiency). vs build operations slower larger projects:
a project centralized list of data templates have lot of things above in dependency stack, causing numerous other projects rebuilt after every change
any project central repository of grow large , take long time compile (5 seconds /project limit while i'm actively developing xaml, cap @ 10 seconds entire build operation , start debugging)
the biggest problem have silly xaml namespace references (clr-namespace:). need updating point new home assemblies (assembly=)
generally, resharper great job, when refactorig xaml. analyzes xaml files, , fixes wrong xml namespaces. however, need go trough files, 1 one.
you can use plain find/replace dialog , replace
;assemmly=tempprojectempty string. write powershell script that, if need more often.and revert out afterwards don't accidentally promote temporary xaml changes source control?
you need carefull when doing check-ins, compare files original version , investigate changes
however, there 1 solution you. split projects wpf usercontrol libraries. not testing purposes, permanently. try break large resource files. don't use practices common place put stuff when working on large projects. consider using loosely coupled design , ioc (assembly injection instead of direct references) when possible. create shared assembly, other assemblies reference. don't create component references lot of other components, let others inject instead. take @ prism insipration: http://www.pluralsight.com/courses/prism-introduction
Comments
Post a Comment