I just upgraded from trial to "paid" version of Telerik Reporting (v5.0.11.316) and now when I try to configure the Object Data Source (via the Wizard) to point to a custom type I defined in the same project as the Reports , it is unavailable in the "Available data source types list". Other types/classes in referenced projects are available.
The Object Data Source binding at run-time is still working OK but not having the meta data on the types available while laying out/building the reports is a pain. The "trial/demo" version did not have this issue. Thx!
The Object Data Source binding at run-time is still working OK but not having the meta data on the types available while laying out/building the reports is a pain. The "trial/demo" version did not have this issue. Thx!
9 Answers, 1 is accepted
0
Hi Mike,
We're sorry to hear you're experiencing problems with the ObjectDataSource component. Its Available data source types tab lists all available types that can be used with the ObjectDataSource component. That includes all public, non-abstract, non-generic classes and structures from the current project and from all other referenced projects. The types are organized in a hierarchical manner grouped by namespace. ITypeDiscoveryService is used to get all types and it filters the static classes. If your class declaration contains the static keyword - either remove it or manually define the type of the class in the report constructor.
If the desired type does not appear in the list, make sure the current project is built.
If the issue persists, we would need your project so we can test on our end what is happening and why it cannot be seen.
All the best,
Steve
the Telerik team
We're sorry to hear you're experiencing problems with the ObjectDataSource component. Its Available data source types tab lists all available types that can be used with the ObjectDataSource component. That includes all public, non-abstract, non-generic classes and structures from the current project and from all other referenced projects. The types are organized in a hierarchical manner grouped by namespace. ITypeDiscoveryService is used to get all types and it filters the static classes. If your class declaration contains the static keyword - either remove it or manually define the type of the class in the report constructor.
If the desired type does not appear in the list, make sure the current project is built.
If the issue persists, we would need your project so we can test on our end what is happening and why it cannot be seen.
All the best,
Steve
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
chris_cf
Top achievements
Rank 2
Rank 2
answered on 22 Sep 2011, 05:22 AM
How do you manually define the type of the class in the report constructor?
0
Hugo Esperanca
Top achievements
Rank 1
Rank 1
answered on 24 Sep 2011, 11:32 AM
This never worked for me. It doesn't matter what I do the data source types list is always empty.
The Telerik videos make things look so easy but unfortunately, with most of the Telerik product we have purchased so far, it's never that way. I had to give up using the data source wizard in the end and code it all myself.
The Telerik videos make things look so easy but unfortunately, with most of the Telerik product we have purchased so far, it's never that way. I had to give up using the data source wizard in the end and code it all myself.
0
Hugo Esperanca
Top achievements
Rank 1
Rank 1
answered on 24 Sep 2011, 01:49 PM
Ok. I've now spent some time looking into this. It looks like if the assembly name contains '.' (dots) the "Available data source types" list will allways be empty. Given that most assembly names follow the convention "CompanyName.ProductName.dll" I suggest that this is something that Telerik should fix. I'll submit a support ticket just to make sure it's logged properly.
0
Hi Hugo Esperanca,
According to our tests, the usage of the dot ('.') character in the assembly name does not seem to cause any problems with ObjectDataSource Wizard. In fact, our own demos have a dot character in the assembly name (e.g. CSharp.ReportLibrary), and the wizard recognizes all the types successfully. It is possible that you have stumbled upon an old bug that filters out all types from all assemblies which start with 'Telerik', however this have been resolved in the most recent version of the product, and assuming that you follow the assembly naming convention guideline: '<company name>.<product name>' you are not supposed to experience that problem in the first place. Nevertheless, if the problem persists with the latest version of the product, we would appreciate if you can send us a small sample project to reproduce it locally.
Regards,
Ivan
the Telerik team
According to our tests, the usage of the dot ('.') character in the assembly name does not seem to cause any problems with ObjectDataSource Wizard. In fact, our own demos have a dot character in the assembly name (e.g. CSharp.ReportLibrary), and the wizard recognizes all the types successfully. It is possible that you have stumbled upon an old bug that filters out all types from all assemblies which start with 'Telerik', however this have been resolved in the most recent version of the product, and assuming that you follow the assembly naming convention guideline: '<company name>.<product name>' you are not supposed to experience that problem in the first place. Nevertheless, if the problem persists with the latest version of the product, we would appreciate if you can send us a small sample project to reproduce it locally.
Regards,
Ivan
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>
0
bohebolo
Top achievements
Rank 1
Rank 1
answered on 07 Oct 2011, 10:47 AM
Same issue with me, any clue how to fix this?
Currently using Telerik.Reporting ver 5.0.11.328
edit:
If I change the platform target of the assembly to "Any CPU" or "x86", then everything works fine.
However I build app targeting x64 environment/platform.
Currently using Telerik.Reporting ver 5.0.11.328
edit:
If I change the platform target of the assembly to "Any CPU" or "x86", then everything works fine.
However I build app targeting x64 environment/platform.
0
Hi Bohebolo,
The reason why you cannot see any types from the x64 assembly is because x86 and x64 assemblies cannot be mixed together. Please, keep in mind that Visual Studio is a 32-bit application, so the designer is restricted to x86 mode even on x64 platforms, which prevents it from discovering any types from x64 assemblies. Since we cannot change that fact, there is nothing we could possibly do to correct the problem on our end. Our advice is to use different platform configurations for the different builds: for "Debug" builds, it is best to use "Any CPU", while for "Release" builds you can use "x64" instead.
All the best,
Steve
the Telerik team
The reason why you cannot see any types from the x64 assembly is because x86 and x64 assemblies cannot be mixed together. Please, keep in mind that Visual Studio is a 32-bit application, so the designer is restricted to x86 mode even on x64 platforms, which prevents it from discovering any types from x64 assemblies. Since we cannot change that fact, there is nothing we could possibly do to correct the problem on our end. Our advice is to use different platform configurations for the different builds: for "Debug" builds, it is best to use "Any CPU", while for "Release" builds you can use "x64" instead.
All the best,
Steve
the Telerik team
Q2’11 SP1 of Telerik Reporting is available for download (see what's new). Get it today.
0
bohebolo
Top achievements
Rank 1
Rank 1
answered on 13 Oct 2011, 03:29 AM
It would be better, if the designer can display error message regarding this issue.
Instead of display nothing in the wizard, that can make users clueless.
Edit:
Steve, I can't mark your post as an answer since no button for that (usually there is a button).
Instead of display nothing in the wizard, that can make users clueless.
Edit:
Steve, I can't mark your post as an answer since no button for that (usually there is a button).
0
Hi Bohebolo,
We use ITypeDiscoveryService Interface to discover available types at design time which is the legitimate way. This interface does not have the ability to identify whether the assembly is x86 or x64.
As for the "Mark as Answer", this can be done only from the person who opened the forum post.
All the best,
Steve
the Telerik team
We use ITypeDiscoveryService Interface to discover available types at design time which is the legitimate way. This interface does not have the ability to identify whether the assembly is x86 or x64.
As for the "Mark as Answer", this can be done only from the person who opened the forum post.
All the best,
Steve
the Telerik team
Q2’11 SP1 of Telerik Reporting is available for download (see what's new). Get it today.