Report Designer Not finding reports in dll

[Don]

Environment Visual Studio 2012, Windows 7 Report Designer latest

I've created a couple of reports in Visual Studio in a project called CdssReportsNew and a folder called Reports
In report designer Open report... and navigate to the bin Debug directory
Select the the CdssReportsNew.dll and open 
Reporting Import Wizard appears but no reports to import

Test by creating new Report called Report1 in Visual Studio. Report1 shows up in the import wizard (although i think not immediately)

change the namespace for my reports from CdssReportsNew.Reports to CdssReports and move them to the root of the project directory

Still not able to find them in the Import wizard.

Any other suggestions?

Thanks,
Don Rule
http://translationalsoftware.com

One thing occurs to me and wondering if it is important. In the reports that I am having trouble with I have a number of references to a business object that look like this

            this.objectDataSource7.DataMember = "CaseInfos";
            this.objectDataSource7.DataSource = typeof(CdssReports.Models.PatientReportContext);
            this.objectDataSource7.Name = "objectDataSource7";

Would the designer ignore these reports if it didn't understand CdssReports.Models.PatientReportContext?

[Don]

Moving this to the Report Designer specific thread

[Stef]

Hello Don,

Please check whether the reports in CdssReportsNew.dll are built against the same Reporting version as of the used Standalone Designer. Otherwise the reports will not be visible in the list.

I hope this helps.

Kind regards,
Stef
the Telerik team

[Don]

Both 7.0.13.220

And the fact that a new (very vanilla) report works leads me to believe that it isn't a versioning issue

Have been able to solve the referenced classes issue by referencing the assemblies in for the standalone designer but still can't see my built reports,

Thanks,
Don

[Elian]

Hi Don,

In order for a report to be imported, it must be first be instantiated. So if a class cannot be instantiated for some reason, it won't be listed as available for export. In your case, as you have said,  the missing type in the DataSource prevents the report from instantiating successfully. 

All the best,
Elian
the Telerik team

[Don]

In the end cut-and-paste from VS to Report tool was easier than figuring it out.
It didn't occur to me to turn on logging in the configuration file but that may have provided some insight into what was failing.