I ended up using SlowCheetah again since it is still working in VS2015, read more here:
<episerver> <sites> <site licenseFilePath="...">
Use ordinary config files transformations available during MSBuild.
We actually delgated this to either TeamCity or Octopus server.
We use standard VS transformnations for this purpose.
On second thoughts, arent those settings gone in the latest versions of EPi?
We have a separate part of our solutino containing "Deployment Items", which can include things like robots.txt for different environments, license files or other environment specific non-config files.
And then we're just doing some powershell magic from our Octopus deploy-server to put the right stuff in based on the environment it's released to. Can also be further generalized to be either for each specific server, or for all servers within an environment.
It's pretty nifty.
Is your apporach working in EPi7.5 and above? From my memory, the site section has been removed from configuration in EPi7.5+
We use the publishing profile instead of standard transformtion to transform the license path based upon different environment. Basically, we include all environment license files in the solution. when our CI (we used Bamboo) kicks off build, it will create a package on the server, so that once build is successful, we can make sure the same code will be deployed to STAGE,UAT and PROD etc.
The license path can be found in EpiServerFramework.config file.
<episerver.framework> <scanAssembly forceBinFolderScan="true" /> <licensing licenseFilePath="./License.config" /> ...... </episerver.framework>
Yes, you are right, license path now is moved to its own element under <episerver.framework>.
I am working with a solution that is going to be hosted in three environments(sites) in Azure and also on the developers local computers and I do not know the best way to handle different license.config for different environments where there are not possible to name them by the name of the server. I need one for development and one that are used on the three Azure-sites.
Anyone else figured out this?