aspnet (repository for Asp.Net Mvc applications, has dependency on main module).main package repository (core/common functionality).You start with top-level module repo which does not have any external dependencies on any other module (core/common functionality). Now when you have decided module boundaries it's time to create repositories for each of the module.

Create Repositories with Submodules Create Main Module Repo This gives nicer debugger experience for developer without any hustle to enable symbols and be able to 'step into' the package source code.

Decision has to be made around type locations - where each type should go and which project will be used where.Īctually for development purposes using ordinary project reference is much more preferred way to work with. It's important to understand where each module ends and where next begins as you be referencing each other through sort of NuGet package references. This is a blog post about the stuff I had to do. So decided to split whole code-base into git submodules and setup separate repositories for each of the sub-systems. abstract/core packages containing only general purpose functionality (like expression tree walker or resource definition attributes)Īs you can see there might be some issue with having multiple purpose packages (with different life-cycles and versions) located in single Git repository.

Later realized that there is actually not so much to do to add support for Asp.Net Mvc (.NET Framework) applications and later also for. Initially there was just a EPiServer package to add support for database driven localization resources. During development of DbLocalizationProvider I had single repository in GitHub containing more that one package as result of the build.

Git submodule init update