Deploy a CLR Trigger/Stored Procedure using WiX

Question

As the founder's of stackoverflow talk so much about being able to deploy changes easy, I'm trying to come up with a solution to solve my issue. A quick background is that a client contacted me and needed something done on the database that is quite not so trivial, but isn't horribly difficult to do (took me about a day to get the procedure to work). Unfortunately, the client needs to be able to deploy this "fix" about 20 times, and without my input, as he isn't going to pay for it.

I have written a CLR trigger that does some work that would otherwise be very difficult using TSQL (xml document transformations.. I'm better at it using CLR vs. TSQL). Deployment is typically a few lines SQL and dumping the dll to a directory from what I can fish out (I've only ever deployed from VS.Net so far).

What I need to be able to do is to provide an MSI installer that will drop the file to a folder, and prompt the user for the database information that is required to connect the CLR procedure to the correct database/table.

Has anyone done this in the past, and if so, are you willing to school someone on how this is done, so I can get this project to bed?

Thanks

I have a similar situation - I'm creating a clr trigger with SharpDevelop, which does not support the 'deploy' action. Therefore, I need to deploy the dll into the database by hand. Did you ever work out the process for doing this? — JSacksteder
– JSacksteder, Commented Jan 10, 2011 at 16:45
the essence is that you have a "Create Extended Procedure" command that you run against the SQL server, and point it to your Dll. I never got the job that I needed this for, so I wound up not getting it solved. Sorry. — Richard B
– Richard B, Commented Jan 21, 2011 at 18:39

Dave Cluderay · Accepted Answer · 2009-04-09 08:14:33Z

2

If you want to avoid the trickiness of placing the file, you can use the alternate form of the CREATE ASSEMBLY statement that specifies the assembly in byte form. e.g.

CREATE ASSEMBY MyAssembly FROM 0xFFFF....;

Obviously, you would have the actual assembly bytes where I've put 0xFFFF.....

answered Apr 9, 2009 at 8:14

Dave Cluderay

7,4661 gold badge33 silver badges29 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Richard B Over a year ago

Hi Dave, I am truly focused on building an MSI installer in this instance.

Collectives™ on Stack Overflow

Deploy a CLR Trigger/Stored Procedure using WiX

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related