Last week we've added the assembly HttpConnector to our current development environment. This assembly was also needed in the multiple demo/customer/production environments.
It appears that this assembly wasn't automatically created on the different environments. Whichresulted in errors in a customer/production environment.
Besides the above assembly we also have more assemblies that need to be passed on to every environment:
It also raises the following questions:
- How do we make the assemblies part of the deployment process and prevent manual work?
- How do we maintain the original .dll files?
- How can we apply newer versions of the assemblies if newer versions are available?
- How can we still apply the assemblies without having to copy the .dll files to every environment?
Best answer by Robbert van TongerenView original
This will result in a script like:
(You can also make a drop and create script)
This script you can put in the upgrade code group:
This way, the script will execute on every environment you roll out.
a 2nd option is when you do want to move the DLL file across, is to create a subroutine with the type DLL assembly, then in the options you can set the name and path for the DLL and the SF will create scripts to create the assemblies.
Hope this helps.
your solution works! We've created a procedure in TSF that includes every (scripted) assembly and assigned it to a 'Manual' code group (which is executed at the very end of every upgrade).