InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comFri, 24 May 2013 11:08:17 GMT20http://www.sqlservercentral.com/Forums/Topic1412111-147-1.aspxExcellent! That is how the GAC is supposed to work. Happy to know you got it sorted. Thanks for posting back.Wed, 27 Feb 2013 09:02:15 GMTopc.threehttp://www.sqlservercentral.com/Forums/Topic1412111-147-1.aspxHi,Thanks for your help. Key files was the issue, I used same in all environments, which resolved the issue. :-)Wed, 27 Feb 2013 01:50:19 GMTmramaswamyhttp://www.sqlservercentral.com/Forums/Topic1412111-147-1.aspxThanks for the information. I wil try this way and keep posted.Tue, 29 Jan 2013 21:49:53 GMTmramaswamyhttp://www.sqlservercentral.com/Forums/Topic1412111-147-1.aspx[quote][b]mramaswamy (1/29/2013)[/b][hr]I found the Key file used to build my custom assembly was different in production region.But I later updated the package using the new build assembly from prod. My assumption is, so after that(package updated with new assembly from prod), whenever the custom assembly rebuild, the package should not fail, as we rebuild already with the assembly from prod.Would that not be the case? please advise me. I am bit confused how things are with.[/quote]As I understand it as long as you keep the version number, name and sign it with the same key the SSIS package will not notice if you redeploy a custom assembly that it references to the GAC.Tue, 29 Jan 2013 21:18:07 GMTopc.threehttp://www.sqlservercentral.com/Forums/Topic1412111-147-1.aspxI found the Key file used to build my custom assembly was different in production region.But I later updated the package using the new build assembly from prod. My assumption is, so after that(package updated with new assembly from prod), whenever the custom assembly rebuild, the package should not fail, as we rebuild already with the assembly from prod.Would that not be the case? please advise me. I am bit confused how things are with.Tue, 29 Jan 2013 19:55:33 GMTmramaswamyhttp://www.sqlservercentral.com/Forums/Topic1412111-147-1.aspxWhen you promote the new assembly into the GAC is it using the same version and public key?Sun, 27 Jan 2013 09:23:12 GMTopc.threehttp://www.sqlservercentral.com/Forums/Topic1412111-147-1.aspxHi,I have two SSIS packages which uses the Custom DLL in a script task. This Custom DLL has code which is not only used by ssis, but various other components in our project. Everytime when the DLL updated for any change in other components(not in the code used by the ssis tasks), the package been failed in the production with the following error."Cannot create user component class. Make sure there is one class marked with SSISScriptComponentEntryPointAttribute in your script. at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.CreateUserScriptInstance() End "Note:whenever the DLL changes, I ensured to register the latest in GAC of the production environment.If I open the script tasks and rebuild the code, it resolves the issue without changing any setting or one line of code.Is this the SSIS necessity to rebuild the tasks if DLL changes or am I missing any setting? Please help me on this.ENV used : SSIS 2008 and .NET 3.5 frameworkNote: I tried setting dealy validation to true also, but no help.Thanks,Sun, 27 Jan 2013 02:12:52 GMTmramaswamy