Package Management, Source Control & Git Deployments to Azure
Looking For Ideas for Third Party Package Referencing in Umbraco
We are a small multi developer team, we started with local versions of the code and database and quickly migrated to a shared sql azure database withe uSync to manage the doc types et al. We are currently wrestling with source control and third party packages for Umbraco and are looking for best practices on how to manage them.
Currently using Umbraco 6.1.6, git (bitbucket) and azure with msbuild
Structure is as follows;
Root
>bin
>Dependancies
>App_Data
>packages
>installed
>installedPackages.config
Currently
When a package is installed we have gone to the bin (bin folder is excluded via .gitignore) and taken a copy of the dll and placed in the dependancies folder (included in git). We then re-add the reference to the project so that we can source control the Dependancies folder.
This works well for when we have a reference in the solution. The problem comes when the reference is not included in the project but rather (I assume) dynamically loaded by umbraco. We have moved the dll files into the dependancies folder and modified the file installedPackages.config to look into the dependancies folder, but when we have done a deployment the reference is not being picked up (there are mutiple components).
Attempting to resolve the problem we have found the following work arounds
Manually install the packages on the server (not ideal for auto builds)
Add the references manually to the solution looking into the dependancies for the binary (getting closer to the ideal)
The problem is we are stuggling to find where the original references are stored in Umbraco to either change or remove them. We do not want to be loading the same assemblies twice (once where it fails to load dynamically through umbraco and once where it succeeds with the manually added references)
Does any one know where these references may live so that we can either remove them or amend them to look into the correct folder.
Package Management, Source Control & Git Deployments to Azure
Looking For Ideas for Third Party Package Referencing in Umbraco
We are a small multi developer team, we started with local versions of the code and database and quickly migrated to a shared sql azure database withe uSync to manage the doc types et al. We are currently wrestling with source control and third party packages for Umbraco and are looking for best practices on how to manage them.
Currently using Umbraco 6.1.6, git (bitbucket) and azure with msbuild
Structure is as follows;
is working on a reply...