Radzen scheduler takes time to load

Radzen.Blazor Components
1

Hi

I am using Radzen Scheduler in my Blazor Server Application

image
image1631×790 28 KB

When I go to the page for the first time. It takes a lot of time to load the scheduler. Afterward, it becomes really responsive.

Can you please tell me whats the issue here

Regards
Saad

2

Do you have the same problem with our demo? Maybe your database access takes longer time.

3

I am testing this issue on my local machine. I believe the calendar libraries are loaded when you visit the page. Once they are loaded it runs smooth

4

@enchev Hello Enchev
This issue only comes on Edge. It is working fine on Chrome and Firefox.

5

I'm afraid I cannot provide any additional info why it is slow on Edge.

6

Should I create an issue in the repository?

7

Not sure how this will help. On my Edge our demo loads instantly:

image
image1920×1080 195 KB

8

This happens with my app as well. The first time it's slow after which it is almost instant. If restart the app in azure and then access the scheduler again I can reproduce it. So it always occurs on the first time I access it. It also happens the first time if I clear all cookies/cache then try to access it.

9

Can you test the suggestion from this github issue? Add this code somewhere in your app so it executes at startup:

class MyCustomTypeProvider : IDynamicLinkCustomTypeProvider
{
    static readonly HashSet<Type> empty = [];
    public HashSet<Type> GetCustomTypes() => empty;
    public Dictionary<Type, List<MethodInfo>> GetExtensionMethods() => throw new NotSupportedException();
    public Type ResolveType(string typeName) => throw new NotSupportedException();
    public Type ResolveTypeBySimpleName(string simpleTypeName) => throw new NotSupportedException();
}

And then in Program.cs do this:

System.Linq.Dynamic.Core.ParsingConfig.Default.CustomTypeProvider = new MyCustomTypeProvider();
1 Like
10

This worked a charm. My scheduler now loads instantly. THANK YOU!

11

Scheduler loads instantly with this update. Hopefully didn't introduce any issues elsewhere. Thank you!