Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Blazor app doesn't load after upgrade to 3.0-preview4/preview5

See original GitHub issue

I have latest extension installed from here. Also VS 2019 16.2.0 Preview 1.0 installed. Code migrated from 0.7.0 using official migration guide.

My app can’t load. Only router exists inside <app>.

Nothing useful in console

Debugging gives me no information at all

My project is available here (branch called feature-blazor-3.0.0-preview4)

Please help me determine what goes wrong. I added some logging inside OnInit(Async) methods of my pages, but they’re never called. I tried to play with Startup file of Server project, but nothing changed.

dotnet --info output:

Пакет SDK для .NET Core (отражающий любой global.json):
 Version:   3.0.100-preview5-011568
 Commit:    b487ff10aa

Среда выполнения:
 OS Name:     Windows
 OS Version:  10.0.17134
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\3.0.100-preview5-011568\

Host (useful for support):
  Version: 3.0.0-preview5-27626-15
  Commit:  61f30f5a23

.NET Core SDKs installed:
  2.1.202 [C:\Program Files\dotnet\sdk]
  2.1.700 [C:\Program Files\dotnet\sdk]
  2.1.800-preview-009677 [C:\Program Files\dotnet\sdk]
  2.2.300 [C:\Program Files\dotnet\sdk]
  3.0.100-preview5-011568 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.2.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.2.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.0.0-preview5-19227-01 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.2.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.0.0-preview5-27626-15 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.0.0-preview5-27626-15 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Issue Analytics

State:
Created 4 years ago
Comments:14 (4 by maintainers)

Top GitHub Comments

1reaction

danroth27commented, May 29, 2019

Thanks @3x0dv5 for helping out here!

@vova-lantsov-dev I’m hoping the pointers from @3x0dv5 are enough to get you unblocked. If you’re still hitting issues that you think are problems we need to address in Blazor please let us know!

0reactions

danroth27commented, May 31, 2019

I also know that there is an issue that components are not visible when usings are declared in _Imports.razor . Is it already reported or I should create new issue?

That’s expected. Layouts in Blazor are components defined by their own class. So using statements in the layout won’t flow into individual pages. To propagate using statements across components you should use _Imports.razor.