Design Preview Not Working

[Zack]

I'm using the latest release - the designer will pull up for an instant, then close again.

Even though I save before previewing, after the designer closes there is an asterisk (*) displayed in the report's tab within Visual Studio.

The Error List has the following Message:

Message 39 You must rebuild your project for the changes to Core.Reports.Customers.CustomerSummaryReport to show up in any open designers. 0 0

I've cleaned and rebuilt the solution.

Using Visual Studio 2012, targeting .NET 4.0.

As per best practices, the report is hosted within its own assembly.

The report was working fine up until I added additional columns to a table within the report detail (increased from 3 to 5).

Any idea how to get this working again?

Thanks in advance,

Zack

[Ivan Hristov]

Hi Zack,

Seems that your report definition has messed up. You could take a look in designer.cs file and remove the added columns manually. The code adding a column to the table should look like this:

this.table1.Body.Columns.Add(new Telerik.Reporting.TableBodyColumn(Telerik.Reporting.Drawing.Unit.Cm(2D)));

The code defining a table column should look like this:

Telerik.Reporting.TableGroup tableGroup1 = new Telerik.Reporting.TableGroup();
.
.
.
tableGroup1.Name = "tableGroup";
tableGroup1.ReportItem = this.textBox9;
this.table1.ColumnGroups.Add(tableGroup1);

Please do not forget to create a backup before making changes to designer.cs file.

Regards,
Ivan Hristov
Telerik

[Brad]

I am having the same issue, except that I am attempting to use a sub report.  If I add a sub report item to my report and preview it, it works fine.  However, as soon as I configure the ReportSource to point to another report within my application, the preview begins to react as stated by the creator of this thread.  The Preview tab will begin to load, then jump right back to the Designer tab.  I haven't found any way of getting around it.

[Nasko]

Hello Brad,

We have replied in your support ticket about the same issue. Since the described behavior is not reproducible at our end, we will need some additional information. Please check your support ticket and elaborate further on the issue there.

Regards,
Nasko
Telerik