I have a large ASP.NET (legacy) application that actually (functionally) consists of two portals. Therefore, I need to divide it into two separate applications in order to facilitate development for each of them.
Of course, there are common opportunities between them. Some of them are in DAL and BL, and this is not a problem. All of these codes were separate, separate projects that made up the assemblies that needed to be referenced in both applications.
But the problem is with some pages, many user controls, some css and javascript files that are shared between two "portals" (applications).
I would like to ask for advice on how to handle them. My main goal is to avoid duplication, so ideally they should stay in one place and be used by both applications.
At first I tried to add files from one project to another as linked files. Although this works for a code file (they are embedded in the project to which they are attached), it is not for aspx / ascx or css / javascript / images. This happens if I publish first (if they are marked as content, they are copied at the time of publication), but I cannot do this all the time during development, and such files are not found when the application is debugged / launched from the source code (sincere, obviously, related files are not actually available in the application file tree when you search for any of them.
, .
Common , , , pre-build xcopy.
, SVN, svn:external, .
. - ? ?
?