Help me refactor our web application
November 11, 2010 3:09 PM Subscribe
What's the best way to break apart an asp.net c# web application?
Over the past few years I've been overseeing the development of a large asp.net web application. We have refactored the application along 3 tier architecture lines - database access and business logic in DLLs, front end in asp.net web forms.
We are rapidly expanding the functionality but the core product is in heavy use. We want to be able to develop and release the new features rapidly while not impacting the tested and stable core of the application. Because of the way asp.net seems to work, though, everything on the gui side is compiled into a large site dll, making the modularization of the front end tricky.
What we would like to do is to break the front end into several projects that compile into separate dlls but can still look like one seamless site - sharing session state, web.configs, etc. Is this possible? Can someone point me to whitepapers that describe this process?
(I imagine some people will suggest "Move to MVC!", but that's not really feasible for us anytime in the near future due to the complexity of our site).
Over the past few years I've been overseeing the development of a large asp.net web application. We have refactored the application along 3 tier architecture lines - database access and business logic in DLLs, front end in asp.net web forms.
We are rapidly expanding the functionality but the core product is in heavy use. We want to be able to develop and release the new features rapidly while not impacting the tested and stable core of the application. Because of the way asp.net seems to work, though, everything on the gui side is compiled into a large site dll, making the modularization of the front end tricky.
What we would like to do is to break the front end into several projects that compile into separate dlls but can still look like one seamless site - sharing session state, web.configs, etc. Is this possible? Can someone point me to whitepapers that describe this process?
(I imagine some people will suggest "Move to MVC!", but that's not really feasible for us anytime in the near future due to the complexity of our site).
This thread is closed to new comments.
I've worked on an ASP.Net site that was split into a front end which made calls to a web service, it's definitely a pain keeping sessions active in sync.
posted by robertc at 3:59 PM on November 11, 2010