I want to ask about this question specifically because it has now become my main holdup.
My solution contains a database project and a single SQL/CLR assembly project.
When I run Build -> Deploy Solution it fails with error 6541: "ALTER ASSEMBLY failed because assembly 'SqlClrAssembly' has more than one file associated with it. Use ALTER ASSEMBLY DROP FILE to remove extra files."
But I if I select Build -> Deploy SqlClrAssembly it works fine.
In the first case it runs a script named after the database project and in the latter it runs a script named after the actual CLR assembly project. This latter script is "better" because it has the DROP FILE option specified for the assembly.
So what is going on here?
Should I run the database project's deploy or just the Assembly project's deploy?
If I should run the database project's deploy how can I force it to include the DROP FILE option in the ALTER ASSEMBLY?
If I should not run the database project's deploy, then why on earth do I even need this database project?
Also, it appears that the .pdb and src files are being deployed intermittently and I have no idea what influences this, if I run a select * on [sys].[assembly_files] it looks like the src and pdb are not there, yet yesterday they were, hence I cannot set
breakpoints or debug.
View Complete Post