1 option is that once the assembly is created on the development server, you can script the assembly into a script via management studio:
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.
Hi Robbert,
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).
