Monday August 3rd

Saturday August 1st

Friday July 31st

Thursday July 30th

Wednesday July 29th

Managing Nested Libraries Using the GIT Subtree Merge Workflow

The Subtree Merge Workflow offers a relatively painless mechanism for managing shared library source code as a component of a larger project. If you have ever had a shared library, custom control, or other component under development that you also wanted to use within one or more dependent projects, you no doubt understand what I mean.

1 comments

This was written pretty agnostically in terms of language/framewrok. However, managing multiple dependent projects within VS was the context from which I was working originally. NOTE: Once you have added a dependent library project as a subtree, it is then necessary to use "Add Existing Project" from the VS Solutions Explorer, as well as Set Project Dependencies just like any other time you add a project to a VS Solution.

Commenting on Stories is limited for now and will open up to those recommended by the community. Learn how
Loading DotNetKicks...
brought to you by the Kicks Network