| |
ActiveReports for .NET 2.0 Support
Started by Nathan Baulch at 05-31-2006 2:26 AM. Topic has 3 replies.
  
|
|
Sort Posts:
|
|
|
|
 05-31-2006, 2:26 AM
|
Nathan Baulch
Joined on 02-13-2006
Posts 21
|
|
|
One of the many subtle changes between .net v1.1 and v2 is that the Type.GetX() methods are no longer guaranteed to return their array elements in the same order.
Unfortunately the ListDataSource relies on this behaviour as it calls GetProperties() many times during its lifetime. This causes my reports to randomly move data all over the place and usually throw an exception as it attempts to force strings into check boxes and format booleans as datetimes.
Fortunately it’s not too hard to implement a custom IDataReader which stores the PropertyInfo[] array rather than calling Type.GetProperties() over and over.
Are there any plans to natively support the IBindingList interface at any stage? This would be a much cleaner and more consistent way to support binding to businesslogic/domain objects (which is only going to get more popular with Microsoft DLinq on its way, although I have no plans to move away from NHibernate anytime soon).
Nathan
|
|
|
|
|
Report
|
|
|
|
|
05-31-2006, 3:42 PM
|
Peter Power - DD
Joined on 08-28-2004
Posts 1,217
|
Re: Bug in ListDataSource...
|
|
|
|
|
|
Nathan,
I have brought this to our development team's attention. I do not believe that this is something in which there are currently plans to support, but may eventually make it into the product if there is enough demand.
Thanks,
|
|
|
|
|
Report
|
|
|
|
|
07-05-2006, 1:58 PM
|
JohnEvaluating
Joined on 07-05-2006
Posts 36
|
Re: Bug in ListDataSource...
|
|
|
|
|
|
 Nathan Baulch wrote: | One of the many subtle changes between .net v1.1 and v2 is that the Type.GetX() methods are no longer guaranteed to return their array elements in the same order.
Unfortunately the ListDataSource relies on this behaviour as it calls GetProperties() many times during its lifetime. This causes my reports to randomly move data all over the place and usually throw an exception as it attempts to force strings into check boxes and format booleans as datetimes.
Fortunately it’s not too hard to implement a custom IDataReader which stores the PropertyInfo[] array rather than calling Type.GetProperties() over and over.
Are there any plans to natively support the IBindingList interface at any stage? This would be a much cleaner and more consistent way to support binding to businesslogic/domain objects (which is only going to get more popular with Microsoft DLinq on its way, although I have no plans to move away from NHibernate anytime soon).
Nathan
|
|
Nathan, could you upload your IDataReader derivative for us to study?
* fixed my original problem, it was a noobie error.
** I am guessing this bug requiring IDataReader derivative is fixed with the ActiveReports3 I am using today, (7/5/2006).
Thanks.
|
|
|
|
|
Report
|
|
|
|
|
09-20-2006, 4:50 PM
|
warnestam
Joined on 04-07-2006
Sweden
Posts 34
|
Re: Bug in ListDataSource...
|
|
|
|
|
|
|
|
|
GrapeCity » Product Support » ActiveReports f... » Bug in ListDataSource...
|
|
|
|
|