Telerik Reporting ObjectDataSource Namespace

[Jose]

I have created .NET Solution which one use the three layers architecture (DAL: APM.DataAccess, BR: APM.BusinessRules, UI: APM (MVC Web Project)), also I have created a reporting based on class .cs (into APM web layer), I mean compiled report (not standalone).  I have created the methods to retrieve data through different layers into my .NET solution.  At the end I want to include an ObjectDataSource (because the data retrieved from different Layer needs be processing in order to complete and show in report) into my compiled report but I can't see the main namespace APM (web layer) which contains my method to retrieve data processed in order to display on the report.   So when I add the ObjectDataSource into report layout, I can see the popup window where I can choose the Namespace and select the method to retrieve data, but here I can't see APM namespaces and I can't choose the right method.  Do you have any idea or comments about it? I attached some images.

I am using the Telerik_Reporting_R3_2016_SP1_10_2_16_1025_DEV.msi

[Jose]

I have tried to solve the problem and I think the issue occurr when the window popup to configure the Object Data Source is displayed,  Basically in this moment the dll file or namespaces into dll doesn´t recognized and I can't see it, of course I can't select it. I have checked the GAC on operative system (windows 10) and my dll: APM.dll doesn´t appear there, I think that is correct. A lot days ago I have worked with another .NET Solution and the telerik Reporting and no problems for that case.

So any comment or/and help to give me some information in order to solve the problem really would be appreciated.

[Todor]

Hello Jose,

ObjectDataSource Wizard will list all available types that can be used with the ObjectDataSource component from the current project and from all other referenced projects which includes all public, non-abstract, non-generic classes and structures organized in a hierarchical manner and grouped by namespace.

If the desired type/namespace does not appear in the list, make sure the current project is built and all necessary project references are added. Have in mind that Visual Studio is a 32-bit application, so the designer is restricted to x86 mode even on x64 platforms, which prevents the ObjectDataSource Wizard from discovering any types from x64 assemblies. The solution is to use different platform configurations: for "Debug" builds it is best to use "Any CPU", while for "Release" builds you can use "x64" instead.
A similar issue has been discussed in our forums and you may find useful the suggested solutions in the forum thread: Custom Type/Class unavailable in Configure Object Data Source Wizard.

I would also suggest you to check the ObjectDataSource component troubleshooting help article to avoid issues when previewing reports that use ObjectDataSource.

I hope the provided information would help resolving the issue.
If the problem persists, I would appreciate it if you sent us a runnable sample project that experiences the issue, so that we could investigate it and provide you more specific advises.

Regards,
Todor
Progress Telerik

[Mark]

I hate to open an old post, but, I am having this issue. It's not picking up any classes from one of my referenced assemblies.  I have read through the articles listed in the post and seem to be doing everything correctly.  In fact, it can't find anything from the current assembly. It's weird.  Any help would be greatly appreciated.

 

Thanks

[Todor]

Hello Mark,

The information is not sufficient to provide any specific advices.
Consider opening a support ticket and attaching the project for investigation.

Regards,
Todor
Progress Telerik

[Mark]

Not sure what more information I can give you.  We have 4 projects in our solution. The reports are being designed in Solution 1, Not a single Object form Solution 1 shows up to be picked, which I find it funny, as it is in the same solution and namespace as the report layout.  Most of the objects in which we want to reference are in Solution 2, however, not a single one show up.  Funny how any objects in Solution 3 do show up.  Only Objects in Solution 3 show up.

[Mark]

Where I said Solution 1, Solution 2, Solution 3, I meant Projects 1, 2, and 3

[Todor]

Hi Mark,

In the ObjectDataSource we use the Visual Studio ITypeDiscoveryService to find the available types. I suspect that the service has failed while going through the assemblies of the project. The issue can be investigated further by debugging the Visual Studio Report Designer with another Visual Studio instance - Attach to Running Processes with the Visual Studio Debugger.

The problem has occurred few times before - in all cases the projects have had a large number of referred assemblies. Separating the reports/data providing types in dedicated ReportLibrary/ClassLibrary projects has always solved the problem.
You can test to extract all ObjectDataSource types in dedicated ClassLibrary project(s).

Regards,
Todor
Progress Telerik

[Mark]

What's funny, is the project/namespace in which I am trying to get the data from is library of objects.  The only thing else that is in that project is a DBML.  It could be the size of our assembly. I will have to look more into your suggestion of debugging it.

[Darrin]

I know this is dated, but I had a similar issue trying to get the standalone Report Designer to recognize my assembly.

I created a separate class library, copied the MyData.dll to the Report Designer installation folder then modified the ReportDesigner.exe.config file to include the assembly reference. 

Solution:
After beating my head on the desk for a few hours trying to get this to work, I realized that my project was an Asp.Net core application and so was my class library. I deleted the Asp.Net core class library proejct and created a new class library based on .Net Framework 3.0

Repeated the copy procedure to the report designer folder and now the Report Designer discovers my custom data objects.

I hope this helps someone in the future.