Reputation: 1074
I currently know of a solution for creating "child" web application projects in VS that is detailed here. However that solution was detailed for VS2005. It still works in VS2010, however it looks like there are still a few issues with it as it is effectively a VS hack.
I was wondering if there has been anything new/better in VS2008 or VS2010 to better support splitting up a web project - I can't find anything on it.
Thanks.
Upvotes: 3
Views: 3560
Reputation: 4922
I did this for my organisation and wrote this blog after completion: http://abhighag.blogspot.com/2012/03/separate-web-application-into-multiple.html
Thought it might be useful for some one else :)
Upvotes: 2
Reputation: 1074
As an update on this, I decided not to use child web projects. I still feel like they're a hack and wasn't prepared to deal with any future unknowns.
It seems like there is no other way of achieving what I want, so I decided to go with one big Web Application project.
Upvotes: 1
Reputation: 30152
What are the issues? This isn't a hack - you are just changing the default project template to suit your needs and that you are going to rely on asp.net's web.config inheritence for projects under the same folder structure.
These are still conceptually separate applications but you are sharing either a web.config on inheriting settings from the parent. By using IIS and not the built in web server you are truly getting the full working inheritence. Plus - cassini (built in web server) is slow and act different than IIS anyways - even more reason to just use IIS or IIS Express.
Upvotes: 0