Custom User Functions in Expressions Window in Visual Studio?

[Keith]

Hello! 

I am attempting to create a custom user function as per: http://www.telerik.com/help/reporting/expressions-user-functions.html

I created my custom assembly, and was able to successfully get the new function to show up in the standalone Telerik Report Designer Expressions Window. 

However, I can't seem to get this same custom assembly to show up in the expressions window in the Visual Studio Report Designer for Telerik. I was not able to find the right search terms to find a solution to my issue anywhere. I'm sure there is something simple that I am missing to have the visual studio report designer load the custom assembly in the Expressions Window. Can anybody help me out? I've added a reference to the assembly DLL file in my project, and I've updated app.config as below:

<?xml version="1.0" encoding="utf-8" ?><br>
<configuration><br>   
<configSections><br>     
<section<br>             
name="Telerik.Reporting"<br>             
type="Telerik.Reporting.Configuration.ReportingConfigurationSection, Telerik.Reporting"<br>              allowLocation="true"<br>             
allowDefinition="Everywhere"/><br>   
</configSections><br>  <br>  <br>   
<connectionStrings><br>    my connection info in here! <br>    </connectionStrings><br><br> 

<Telerik.Reporting><br>   
<AssemblyReferences><br>     
<add name="CustomAssembly"/><br>   
</AssemblyReferences><br> 
</Telerik.Reporting> <br>  
<br></configuration>

Any guidance that could be offered would be greatly appreciated as I have exhausted everything I can think of. 

 I am using Telerik 2014 Q1 and Visual Studio 2010. 

Thank you! 

[Stef]

Hi Keith,

You need to extend the start application in a similar way as the Standalone Designer. More details about the required settings are available in the Deploying trdx (XML report definition) that uses external assembly KB article.

When you run the preview in Visual Studio, the start application is Visual Studio devenv.exe and settings must be added to devenv.exe.config.


I hope the above information helps you.

Regards,
Stef
Telerik

 

 

[Keith]

Thanks Stef! It was the devenv.exe.config piece that I was missing. I'm off and running in the right direction now!