Custom library Use

When I had used SQL2K5 Sept. CTP there was an issue using custom .net framework 2.0 library. I had to register the library in GAC + had to copy the dll into .Net framework 2.0 folder structure. I understand why we need to copy the dll on the development box so we can build packages, but why do I need to copy the dll in framework folder for production environment. Should GAC registration be enough?

If this is a feature, what's the purpose of registering the dll in GAC if it requires it to be in folder hierarchy. Especially in .net framework 2.0 so that the reference dialog box can display the component.

The question is if I have custom dll how do I deploy it so that it works with the package? How can I use the same dll in development environment without having to copy it in .net framework folder?

You need to put the DLL in the Framework folder if you are calling it from a script task or script component. You only have to do this on your development workstation.

More info here: http://blogs.conchango.com/jamiethomson/archive/2005/11/02/2341.aspx

-Jamie|||

The DLL should be in Frameworks folder at runtime only if the script task's or component's PreCompile option is set to FALSE. In this case the script is compiled at runtime, and the dependency needs to be in the Frameworks folder due to VSA limitations.

In default case when PreCompile is TRUE, the DLL only needs to be deployed to GAC at runtime.

|||That was it. I found a script task that did not have PreCompile set to True.

Thank you.

Custom Assembly Problems

Hi All,
I am having a problem with a shared assembly I created. I created a
dll and registered it in the GAC of my development machine. Then I
added a new key into my system registry so I could add it into a
project easily when in Visual Studio. It works well when I reference
it in my ASP.NET/VB.NET applications.
In reporting services, I added the reference to the dll in my report
just fine. I call a function in the custom report code, which
references my dll. The function returns a boolean which, within an
"IIf" statement, determines the background color of certain cells. It
does the job, builds without errors or warnings, and previews in
Visual Studio just the way it should. However, after deploying to my
production server, it seems like it is basically ignoring my call to
the shared assembly. I get no errors or warnings, but the background
color of the mentioned cells never gets set.
Is there another reference I am missing? Any other suggestions?
Thanks in advance!Some basic stuff which you may have already tried
1. Extend your assembly code to output a "hello world" string. Do this
by using a variable , setting its value through a parameter and use
error handling to output any errors , instead of the parameter string,
in case of errors.
2. Create a blank report and use the function call to display the
string in a text box
3. Deploy your assembly to the production GAC
4. Deploy your report to the production GAC
If that works , use the same function call to perform bits of your
original code and return a "done" string or the error string after the
function is completed .
That should help you in finding out where you are getting issues.
Best of luck
Cheers
Shai|||How do you deploy a report to the GAC?|||On Nov 30, 6:48 am, John <john.n.b...@.gmail.com> wrote:
> How do you deploy a report to the GAC?
Sorry , thats was a typo. I meant deploy the report to production
environment
Cheers
Shai