More instrutions for Run locally needed #1929

Closed
opened 2026-01-29 18:15:45 +00:00 by claunia · 2 comments
Owner

Originally created by @Anspitzen on GitHub (Dec 16, 2025).

Is your feature request related to a problem? Please describe.
The instructions on how to run the demo and pages locally is too vague and will in most cases simply not start.

Describe the solution you'd like
Some more informations on what Project to start, in which of the provided configurations.

Describe alternatives you've considered
Clicking untill it works. Unfortunately it does not work as much as I would like.

Additional context
Maybe I'm just stupid, but the current demo is not starting on my local build.

What I did:
Cloning Repo from github to local.
Opening Radzen.sln. (I also did test with the Server version, same results)
Hitting Run (profile: Radzen.Blazor)
Error: A project with output type of Class Library cannot be started directly. In order to debug this project, add an executable project to this solution which references the library project. Set the executable project as the startup project.

Well, lets change the startup project:
Set RadzenBlazorDemos.Server as Startup project
Hit Run (profile: RadzenBlazorDemos)
Build Failed (Visual studio <v18 does not support target runtime net10.0)

Fixing Target runtimes on RadzenBlazorDemos and RadzenBlazorDemos.Server to net9.0
Build Failed, package refrences for WebHost/EfCore 10.xxx not supported on runtime 9

Fixing these references to 9.xxx on the RadzenBlazorDemos.csproj
Running again
Browser starting, App crash instantly:
Microsoft.JSInterop.JSException: Could not find 'Radzen.preventArrows' ('Radzen' was undefined).
Error: Could not find 'Radzen.preventArrows' ('Radzen' was undefined).
at blazor.web.js:1:384
at Array.forEach ()
at l.findFunction (blazor.web.js:1:352)
at _ (blazor.web.js:1:5101)
at blazor.web.js:1:2894
at new Promise ()
at w.beginInvokeJSFromDotNet (blazor.web.js:1:2857)
at vn._invokeClientMethod (blazor.web.js:1:65751)
at vn._processIncomingData (blazor.web.js:1:63140)
at :44398/connection.onreceive (https://localhost:44398/_framework/blazor.web.js:1:56781)
at :44398/Microsoft.JSInterop.JSRuntime.InvokeAsync[TValue](Int64 targetInstanceId, String identifier, Object[] args)
at :44398/Microsoft.JSInterop.JSRuntimeExtensions.InvokeVoidAsync(IJSRuntime jsRuntime, String identifier, Object[] args)
at :44398/Radzen.Blazor.RadzenListBox`1.OnAfterRenderAsync(Boolean firstRender) in C:\Users\blume\source\repos\radzen-blazor\Radzen.Blazor\RadzenListBox.razor.cs:line 152
at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(:44398/Task taskToHandle, ComponentState owningComponentState)

When looking up the <script src="/_content/Radzen.Blazor/... in browser dev tools
It is not loaded. When opening script in new tab it again throws me to the starting of the app where this script is still missing ...

Originally created by @Anspitzen on GitHub (Dec 16, 2025). **Is your feature request related to a problem? Please describe.** The [instructions](https://github.com/radzenhq/radzen-blazor?tab=readme-ov-file#run-demos-locally) on how to run the demo and pages locally is too vague and will in most cases simply not start. **Describe the solution you'd like** Some more informations on what Project to start, in which of the provided configurations. **Describe alternatives you've considered** Clicking untill it works. Unfortunately it does not work as much as I would like. **Additional context** Maybe I'm just stupid, but the current demo is not starting on my local build. What I did: Cloning Repo from github to local. Opening Radzen.sln. (I also did test with the Server version, same results) Hitting Run (profile: Radzen.Blazor) Error: A project with output type of Class Library cannot be started directly. In order to debug this project, add an executable project to this solution which references the library project. Set the executable project as the startup project. Well, lets change the startup project: Set RadzenBlazorDemos.Server as Startup project Hit Run (profile: RadzenBlazorDemos) Build Failed (Visual studio <v18 does not support target runtime net10.0) Fixing Target runtimes on RadzenBlazorDemos and RadzenBlazorDemos.Server to net9.0 Build Failed, package refrences for WebHost/EfCore 10.xxx not supported on runtime 9 Fixing these references to 9.xxx on the RadzenBlazorDemos.csproj Running again Browser starting, App crash instantly: Microsoft.JSInterop.JSException: Could not find 'Radzen.preventArrows' ('Radzen' was undefined). Error: Could not find 'Radzen.preventArrows' ('Radzen' was undefined). at blazor.web.js:1:384 at Array.forEach (<anonymous>) at l.findFunction (blazor.web.js:1:352) at _ (blazor.web.js:1:5101) at blazor.web.js:1:2894 at new Promise (<anonymous>) at w.beginInvokeJSFromDotNet (blazor.web.js:1:2857) at vn._invokeClientMethod (blazor.web.js:1:65751) at vn._processIncomingData (blazor.web.js:1:63140) at :44398/connection.onreceive (https://localhost:44398/_framework/blazor.web.js:1:56781) at :44398/Microsoft.JSInterop.JSRuntime.InvokeAsync[TValue](Int64 targetInstanceId, String identifier, Object[] args) at :44398/Microsoft.JSInterop.JSRuntimeExtensions.InvokeVoidAsync(IJSRuntime jsRuntime, String identifier, Object[] args) at :44398/Radzen.Blazor.RadzenListBox`1.OnAfterRenderAsync(Boolean firstRender) in C:\Users\blume\source\repos\radzen-blazor\Radzen.Blazor\RadzenListBox.razor.cs:line 152 at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(:44398/Task taskToHandle, ComponentState owningComponentState) When looking up the <script src="/_content/Radzen.Blazor/... in browser dev tools It is not loaded. When opening script in new tab it again throws me to the starting of the app where this script is still missing ...
Author
Owner

@akorchev commented on GitHub (Dec 16, 2025):

Hi @Anspitzen,

We will update the Running demos instructions to mention that .NET 10 support is needed. Other than that everything should work out of the box in Debug configuration.

@akorchev commented on GitHub (Dec 16, 2025): Hi @Anspitzen, We will update the [Running demos](https://github.com/radzenhq/radzen-blazor?tab=readme-ov-file#run-demos-locally) instructions to mention that .NET 10 support is needed. Other than that everything should work out of the box in Debug configuration.
Author
Owner

@Anspitzen commented on GitHub (Dec 16, 2025):

Ok, I did install Visual Studio 2026 now (nomaly using the 2022).
After a fresh clone from remote repository the startup did work again out of the box

@Anspitzen commented on GitHub (Dec 16, 2025): Ok, I did install Visual Studio 2026 now (nomaly using the 2022). After a fresh clone from remote repository the startup did work again out of the box
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/radzen-blazor#1929