Best practices for enterprise web solutions
hi!
in our organization have 3 independent webportal development teams. each of teams have 1 solution specific code/binaries/pages , resources. in addition, have 1 framework solution containing common code , resources - such common aspx pages, usercontrols, masterpages, images, css, common code libaries, wrappers , such. common libaries compiled every subsolution teams can develop , release solutions independently (as long coordinate changes in common libaries), other resources (images, css, etc.) copied each solution when deploying.
sum up, have 1 framework solution , 3 independent web- solutions reuse common resources framework.
problem have reusing common resources efficiently in subsolutions. reusing common libaries handled (referenced subsolutions), have issues when reusing uncompiled resources such pages, usercontrols, images , css framework solution. today half-way around issue defining virtual <master> folder (using iis) in subsolutions pointing master folder in framework solution. consumer solution able access , compile framework resources runtime.
unfortunately, approach resources not avaliable @ designtime. no intellisense framework usercontrols registered pages in subsolutions, cannot use design view aspx pages inherit master pages framework, css, , on - because actual path frameworkitems not exist.
1 solution include common resources framework each solution, seem activate source control items in solutions - , not want. wish keep each solution independent, , reuse resources framework solution without having include resources solution files consumer solutions.
best practices/patterns dealing kind of setup?.
not sure if appropriate forum question, hope able this. :)
yours sincerely,
markus nordstrønen
in our organization have 3 independent webportal development teams. each of teams have 1 solution specific code/binaries/pages , resources. in addition, have 1 framework solution containing common code , resources - such common aspx pages, usercontrols, masterpages, images, css, common code libaries, wrappers , such. common libaries compiled every subsolution teams can develop , release solutions independently (as long coordinate changes in common libaries), other resources (images, css, etc.) copied each solution when deploying.
sum up, have 1 framework solution , 3 independent web- solutions reuse common resources framework.
problem have reusing common resources efficiently in subsolutions. reusing common libaries handled (referenced subsolutions), have issues when reusing uncompiled resources such pages, usercontrols, images , css framework solution. today half-way around issue defining virtual <master> folder (using iis) in subsolutions pointing master folder in framework solution. consumer solution able access , compile framework resources runtime.
unfortunately, approach resources not avaliable @ designtime. no intellisense framework usercontrols registered pages in subsolutions, cannot use design view aspx pages inherit master pages framework, css, , on - because actual path frameworkitems not exist.
1 solution include common resources framework each solution, seem activate source control items in solutions - , not want. wish keep each solution independent, , reuse resources framework solution without having include resources solution files consumer solutions.
best practices/patterns dealing kind of setup?.
not sure if appropriate forum question, hope able this. :)
yours sincerely,
markus nordstrønen
how common uncompiled resources change?
Architecture > Architecture General
Comments
Post a Comment