2 errors with RBS 1.07

Hello radzen team,
im going on to try to work with RBS but there are some errors...

  1. Message "Failed to fetch"
  2. Can't fetch Roles

s. Video

I have a version without the Devexpress Dependencies.
Should a send you my project to info@radzen.com?

Kind regards
Thomas

RBS can only fetch roles in applications that use ASP.NET Identity datatables (AspNetRoles). Not sure if you are using it or not.

Yes.

Hi @korchev,
indeed i use asp.net Identity Tables.

Mail with Project is on the way now.

Thomas

another poi...

When i open a page with syncfusion components in RBS i see a license message from syncfusion.
This message is shown only in RBS. The license key is implemented correct in startup.

You can see the message here for example:

Thomas

Nothing has arrived from you yet. Bear in mind the attachment size.

hi @korchev,
i have send a link for download. Size is 6 MB. i got no message that the mail attachment is to big.

Greets
Thomas

Hi @Thomas,

Thank you for providing the project. We reproduced the problems but will need some more time to find the best solution.

The problem appears in pages that use a class which has a parameter of type TrentService. RBS fails to instantiate an instance of such classes in design time.

I will notify you by email when we have a solution for this.

You can solve this by moving the license registration code from OnConfigure to OnConfigureServices.

Hi @korchev,
Thanks for info about syncfusion license!

looking forward using RBS!

Thomas

hi @korchev,
i wish you and the whole Radzen team a happy new year!

You have any news about the "failed to fetch" & "can't fetch roles" problems?

Kind Regards
Thomas

We are working on that issue still (failed to fetch). . Supporting your project requires a rewrite of a major RBS feature so it would take some time to properly develop and test it. The other issue (about roles) seem to be coming from a trailing comma in the appsettings.json file - we will see if we can somehow support that

Thanks for info and your fantastic work!
RBS seems to be a milestone in RAD!

Thomas

Hi @korchev ,
are there any news about my problems with RBS?

Greets
Thomas

Hi @Thomas,

We will work on this issue again probably next month. I will ask you for an up-to-date version of your application to test further. I can also send you a work-in-progress build (not fully tested) which you can try.

Hi @korchev,
i will create a test version of the actual version for you and yes... im looking forward to test the w-i-p version of RBS.

Thomas

Hi @korchev ,
Reviving this thread because the same "Failed to fetch" symptom still happens in RBS 1.63.0 on .NET 10.

Observation in our project:

  • CLI analyze on the full solution returns OK for all 100+ pages, Success at the end.
    dotnet "C:\Program Files\Radzen Blazor Studio\resources\Radzen.Server\Radzen.Server.dll" --analyze
  • In the IDE designer preview the error is random. First ( or sometimes more then one ) page opens fine, a second page fails, or the reverse, with no
    consistent trigger. Restarting RBS helps temporarily.
  • %APPDATA%\Radzen Blazor Studio\log.txt has no exception at the moment the fetch fails.

Project profile that may be relevant:

  • Blazor Web App, InteractiveServer, prerender: false
  • 100+ pages in Components/Pages/, multi-tenant, 3 DbContexts (2 domain + Identity)
  • Program.cs registers: AddFido2(), Session middleware, OData endpoints, HttpClient factory with cookie propagation,
    role self-seeding on startup
  • Custom SafeDynamicLinqTypeProvider to skip bad assemblies during Dynamic LINQ scans
  • Some .razor.cs files are large (around 5800 lines)
  • A clean .Net 10 App from the template does not reproduce this

@korchev the 2022 thread mentioned the root cause was about RBS failing to instantiate classes at design time when
constructor parameters are involved, and a WIP version was offered at some point. Did that rewrite land in a later
release? If not, is there a current way to tune the fetch timeout or isolate which page triggers the state?

CLI analyze output available if needed.
Kind Regards, Mehmet

Yes, that rewrite has long been released. The Failed to fetch error happens when the server process crashes for some reason (usually due to unhandled exception).

If you find a way to reproduce the problem in a consistent manner feel free to send us the app to info@radzen.com.