I have some custom functions in a "new" DLL (myDLL2) that I have been trying to use in the GetValue method of a calculated field in the report designer scripting.
But I keep getting an error (when previewing report) saying I might be missing an assembly reference.
(I have added "using myDLL2;)
If I use the property "ScriptReferencesString" and provide a full path to myDLL2, I am able to see my custom methods which I expect, and it works great.
However, I am also able to reference custom methods in another existing assembly (myDLL1) within the solution.
(if I add "using myDLL1;)
My question is, how am I able to see methods in myDLL1, when it was NEVER added to "ScriptReferencesString".??
Something somewhere is allowing the report designer scripting to see the first DLL, which I do not want to allow users to be able to do.
So while I understand on some leverl the need to register DLLs using the ScriptReferencesString property, what I don't understand is how I'm able to see methods in other customs DLL that I have not registered.
Is your intention to post an answer to your own question?
- If so, then proceed.
- If you simply wanted to post additional information, ask for further clarification, or to just say "Thanks!", please click Leave a Comment.
- If you wish to edit your original question, please use the Edit button in the Toolbox at the top right corner of that entry.