Hello team,
Using RBS 1.21.0 some of the project pages will no longer render in the IDE designer.
Those same pages render correctly using the previous RBS version 1.20.8
The error appears to be related to an added library NetTopologySuite however I created a simplified project using the same library and it renders without error in the designer using the latest version RBS 1.21.0.
Also everything appears to work correctly at runtime.
The error exception stack reported is
Hi @mumfie,
We will need access to your project so we can see why this error occurs. Unfortunately we can't determine the cause from the stacktrace alone.
Hello @korchev,
It seems to be due to a custom property which is also stored in the database as a Point/geography data type used for lat/lng radius searches.
It is defined in the Radzen model classes in Issue.custom.cs.
If the property is commented out the form renders in the designer without error in RBS 1.21.0.
I can't reproduce such an issue just by creating a property using a type from NetTopologySuite. Find attached my test application. The Product class has a Location property but all pages that use it display as expected in design mode. Please let me know how to update that project so it fails as your case.
Net8Auto.zip (405.2 KB)
Hi @korchev,
Yes I have also been trying to recreate the error in a simplfied version without sucess.
I did post the simplified version with database schema/data but as yet unable to reproduce error at GitHub - mumfie2003/RbsNetTopology.
I will rollback the RBS version later today as I know I had to add the conditional compilation RADZEN to overcome a similar error to check if its the same error.
Thanks for your help.
.
Hi @korchev,
Just to confirm it is the same as the original error with 1.20.8 but in that version adding #if !RADZEN to model class prevents the render error.
I will continue to try to build a reproducible sample or maybe move the dependency to the database or api.
This issue was overcome by removing the project reference to NetTopologySuite and using a SQL stored procedure to calculate location and distance.
It is however likely the original issue was related to the forum post
