VS2005 SSIS package not seeing custom task assembly - that has been added to GAC

Question

5.00/5 (1 vote)

See more:

VS2005

1. I have created a custom package, in fact, I created a second one to make sure that the first one did not have problems.
2. Added to the GAC using gacutil
3. Tested the assemblies using a windows form as a test app.
4. Opened up VS2005 and a SSIS project
5. Clicked on ChooseItems from under the general tab, and under SSIS Control Flow Items, it does not show.

I am installing on a production box. When I do this same process on my local, but only it is using VS2008, I see the custom task in the list under the SSIS Control Flow Items. I had thought that the assembly was not in the correct place, but when I look at the paths of the other assemblies, I see all of them are in the path were I placed my custom assembly and used to install in the gac. That is: c:\program files\Micrsoft SQL Server\90\DTS\Tasks\

I am not sure why the dialog box is not displaying my new task assembly when I can test it using a windows app successfully and I can also create SSIS package on my local box. The only thing I can come to the conclusion of is that on my local box, the assembly was compiled.

Does anyone have any suggestions?

Posted 4-Feb-11 7:32am

Randy Kroeger

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Randy Kroeger · Accepted Answer · 2011-02-13T09:23:00

Summary:

My development machine is configured as:
1. VS 2005 - as mentioned, I develop the custom assembly in VS2005
2. VS 2008
3. VS 2010
4. SQL Server 2008
5. Windows 7 OS

The machine that I am deploying my new custom task assembly to is:
1. 2003 OS
2. VS 2005 SSIS

When I deploy this new assembly on this machine (i.e. register in the gac, copy to the tasks folder of the SQL Server directory), I was not able to see the assembly when doing a "choose items".

Resolution:

Copied the project to a machine with the following configuration:
1. 2003 OS
2. VS 2005

I opened this project on this machine and found that all the Microsoft.SqlServer.Dts assemblies showed to be not found when looking under references. I reassigned the assemblies and compiled. I then copied this version the server in which I want to deploy, and everything worked. It is strange, because the version on both machines are the same. The only solution is that the references to these Microsoft.SqlServer.Dts referenced objects of a newer version.

If there are any questions, please let me know.