I have a solution project that consists of database project, CLR database project, C# projects. The database project references the CLR database project. Thus, by clicking deploy on the database project will auto-deploy all projects under the solution. It
is successfully depolyed locally to either SQL Server 2005/2008 wihtout TFS GDR 2.
However, in addition to those compoments, on the staging server, there are TFS GDR 2 and the Windows Server running on virtual machine. The deployment failed. The reason is that my custom SQL CLR assembly that is loaded into database requires other additonal
assemblies. Those assemblies have a dependent hierarchy, which requires deletion in a certain sequence (e.g. assemblyA depends on assemblyB, thus, assemblyB must be deleted from database first before deleting assemblyA.). When the deployment happens on the
staging server, the generated database tsql script try to delete those assemblies, but in a wrong way/sequence. That is the reason it failed. As I said, it is working locally. But local deployment has no TFS GDR2 and virtual machine server, which might or
might not be the cause. Because the auto-generated database script is done via visual studio.
I have tried using the pre/post deployment script, but it still failed on staging server. We want to auto-deploy the solution for staging and production server.
View Complete Post