I checked and noticed that the development team has began in investigation into Case 127559. That issues just didn't fit into the schedule of this most recent release, as you can see the team was busy working on many new things for that release, but I expect upcoming releases to be more frequent now.
Also, I noticed in our internal notes on this case that you can solve the issue with a workaround by just adding a reference to the DataDynamics.Reports assembly to the project. Does this work for you?
Scott Willeke GrapeCity