|
|
Posted by Erland Sommarskog on 11/01/07 08:24
Amber (guxiaobo1982@gmail.com) writes:
>> I learnt just the other day that ALTER ASSEMBLY is not in the repetoir
>> of Visual Studio. I don't use Visual Studio to work with assemblies
>> but stick to the command line. And all impression I get is that
>> using Visual Studio just makes things harder.
>
> It seems Microsoft hasn't done the job well, but if we have a lot of
> objects in the assembly, the manual process of dropping and creating
> them is horrible.
Yes, it's horrible if you have to do it each time you change the
implementation of some single method, and it's amazing that VS cannot
handle this situation.
If you change the interface, it's still a lot of work of course of dropping
and recreating objects. But it is or more less inevitable.
I don't know what's in your assemblies, but I woudl suggest that if you
have a suite of functions and procedures that are independent of each other,
that it's best to have a separate assembly for each function/procedure. Of
course, if they use a lot of common code, you still need to put that common
code in a single assembly in which case you are back to the same situation.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|