I've got a solution in Visual Studio that has an ASP.NET web project as well as some other projects. Everything is in Git. I want to split the functionality of what's now a single website (single web project) into 2 sites (2 web projects) for administrative reasons and I'm looking for recommendations on how to do the split with the least impact on source control and file version history.
One option is to copy the project directories to a 2nd location, designate the source as project 1 and the copy as project 2, then remove the bits of each which aren't needed in their respective projects. The problem with this approach is that I will end up with tons of deletions in Git and I am not sure if I will lose history for the files which are copied to the new location because they'd be new according to Git.
The other option is to create a 2nd project file but leave the underlying source files alone, then modify both project files to point to just their respective relevant bits by doing a "remove from solution" in each. This would modify the .csproj files only which is a much "lighter" change. Naturally of course some files (eg global.cs) will need to exist in both projects and be unique.
I'm sure there are additional options on how to do this, or perhaps better ways of thinking about the problem.
What are some thoughts on accomplishing this split?
via Chebli Mohamed
Aucun commentaire:
Enregistrer un commentaire