Welcome to EMC Consulting Blogs

It's even better if you use $(ProgramFiles) instead of "c:\Program Files\". That way, if you move your project to another machine, that have Program Files on d: drive for example, it will still work.

You also need to have installed the SDK to get gacutil. A common view is gacutil is in the framework and it isn't in 2.0

Jamie,

I've been able to get around the GacUtil requirement by copying the .dll to the assembly folder under C:\Windows. This will autoregister it and make it available....

Scott Barrett

Another useful trick, after the frist time you compile your componet, is to use the Pre-Build to clean out your old version of the componet befre you build the new version. Here is a exmaple of how you might do it.

"$(DevEnvDir)..\..\SDK\v2.0\Bin\gacutil.exe" /uf "$(TargetPath)"
del "c:\Program Files\Microsoft SQL Server\90\DTS\PipelineComponents\$(TargetFileName)"

One northerner to another (maybe North Notts is technically Midlands)

Now all we need is the ability to programmatically add and remove components from the toolbox.  As a packaged software vendor, it's a bit mickey mouse having the user do it manually on install, and really difficult to get them to remember to do it before they install a new version. (In my experience, SSIS is most unhappy if you replace a component in the toolbox with a new version without removing the old one, the next time it starts up)

The death of a package/project due to a new release of a component is also a bunch of laughs.

Here's hoping for more titbits on how to create custom components, deploy them professionally and make them work.

I have had some success with rescuing SSIS projects after a new component build by editing the DTSX manually - attack the DTSExecutable ExecutableType and DTS Name, for a Task in our case and replace it with the new info.  Even if the interface for the component has changed slightly, it seems to deal with that OK.

Also, you can "cleanse" the toolbox when it goes haywire by deleting the toolbox.tbd, in Documents and Settings\<UserName>Local Settings\Application Data\Microsoft\VisualStudio\8.0

Gareth

Hi, I recently installed SQL Server SSIS Sample Component: CodePageConvert (http://www.microsoft.com/downloads/details.aspx?FamilyID=9E56417E-23D1-4FD3-8D6D-61314FAA2DE3&displaylang=en)

When I build this project I get this note on the output:

'gacutil' is not recognized as an internal or external command, operable program or batch file.

Would, please, help me and tell me what to do?

Thank you,

Babak

Babak -

While this is probably too late for you, I've found that you can just drag the .dll into the C:\Windows\assembly folder.  It doesn't want to let you paste it, because it's not actually a file folder, but dragging from one folder to another works.