I'm updating a large asp.net web site project, using VS2013 Ultimate.
Current plans do *not* call for converting this to a web application project or upgrading to MVC, etc.
I'm looking for guidance, links, documentation etc on how I might divide the one large web site project into
three separate web site projects, where the each of the smaller projects could still call
classes and pages in the other projects *OR* learn that that's not possible.
If it is possible, then I also need to learn how to perform the calls between projects.
There is only one developer working on one machine. This is largely proof of concept, so there are no
particular performance or deployment concerns, ALTHOUGH I would like to keep FTP uploads as simple as possible,
because I might set up multiple versions of the same site (to completely segregate functionality among different user groups).
The main driver is to reduce the build time during maintenance, debug and testing. If necessary I can split the
app into three separate solutions, revise, debug and test, and then put them back together again,
although I'd prefer to keep them separate and linked for future maintenance needs.
Any help with this would be appreciated.
Thanks!