Our application is currently made up of two big entities: C# ASPX files, and RPT report template files.
ASPX files are developed by someone, and the RPT files are developed by someone else.
Both worlds are not in sync. For example, you could have 10 new versions for the RPT templates, while only one is done on a C# file.
Is there a way to separate those two logical streams of development part of the same project in SVN? Should everything be kept in the same repository? Would SVN branches be a good application for this?
The way I’d see it would be to have all directories in the same application as such,
- /ModuleA/Main.aspx
- /ModuleB/Admin.aspx
- /ReportTemplates/Generic.rpt
Any guidance would be appreciated!
Thank you
If they are part of the same project, they should be in the same repository. And you wouldn’t need to branch really; one person can work on RPT templates, another person can work on ASPX files, and everyone would get each other’s changes.
Branching would come into play if you had a need to maintain two or more lines of development on the same files. But what you’re describing is the standard, normal use case for Subversion and does not require using branches.