Request For Assistance

[sbwalker]

Mackinnon Buck from the Blazor Product Team is investigating the rendering issue in Oqtane 5.1 which currently requires StreamRendering to be included. The discussion related to this item is in this thread:

dotnet/aspnetcore#54157

As per its usual policy, Microsoft requests a "minimal repro" of an issue in order to investigate (as they do not want to have to deal with setting up app/environment dependencies)... so I was able to repro the rendering issue in the Oqtane SSR POC project. However when Mackinnon clones the repo and runs the project he says that he cannot reproduce the problem.

Are any of you able to clone the repo (https://github.com/oqtane/OqtaneSSR) and run the app and let me know if the Home page displays the following content for you:

I need to determine if my local development environment is the exception case, or if others can reproduce the same problem.

Thank you.

[oqtanecms]

Running the app it looks like:

Uncomment the [StreamRendering] attribute in Routes.razor as shown below:

[krishnavsr]

fresh clone

after uncomment

dotnet --info

.NET SDK:
Version: 8.0.203
Commit: 5e1ceea679
Workload version: 8.0.200-manifests.8cf8de6d

Runtime Environment:
OS Name: Windows
OS Version: 10.0.22631
OS Platform: Windows
RID: win-x64
Base Path: C:\Program Files\dotnet\sdk\8.0.203\

.NET workloads installed:
[maui-windows]
Installation Source: VS 17.9.34714.143
Manifest Version: 8.0.7/8.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\8.0.100\microsoft.net.sdk.maui\8.0.7\WorkloadManifest.json
Install Type: FileBased

[maccatalyst]
Installation Source: VS 17.9.34714.143
Manifest Version: 17.2.8004/8.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\8.0.100\microsoft.net.sdk.maccatalyst\17.2.8004\WorkloadManifest.json
Install Type: FileBased

[ios]
Installation Source: VS 17.9.34714.143
Manifest Version: 17.2.8004/8.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\8.0.100\microsoft.net.sdk.ios\17.2.8004\WorkloadManifest.json
Install Type: FileBased

[android]
Installation Source: VS 17.9.34714.143
Manifest Version: 34.0.52/8.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\8.0.100\microsoft.net.sdk.android\34.0.52\WorkloadManifest.json
Install Type: FileBased

Host:
Version: 8.0.3
Architecture: x64
Commit: 9f4b1f5d66

.NET SDKs installed:
8.0.202 [C:\Program Files\dotnet\sdk]
8.0.203 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
Microsoft.AspNetCore.App 8.0.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 8.0.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 8.0.3 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
x86 [C:\Program Files (x86)\dotnet]
registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

Environment variables:
Not set

global.json file:
Not found

Learn more:
https://aka.ms/dotnet/info

Download .NET:
https://aka.ms/dotnet/download

[mdmontesinos]

Just cloned the repo and launched the project:

After uncommenting StreamRendering:

Tested both with Debugging and Without Debugging and in Debug and Release mode.

dotnet --info (simplified)

.NET SDK:
 Version:           8.0.202
 Commit:            25674bb2f4
 Workload version:  8.0.200-manifests.8cf8de6d

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.19045
 OS Platform: Windows
 RID:         win-x64
 Base Path:   C:\Program Files\dotnet\sdk\8.0.202\

Host:
  Version:      8.0.3
  Architecture: x64
  Commit:       9f4b1f5d66

.NET SDKs installed:
  8.0.202 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 8.0.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 8.0.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 8.0.3 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

[sbwalker]

Thank you @sundnnstore @krishnavsr @mdmontesinos ... the results are inconsistent... but I think I see a pattern.

If you have time could you all do one more experiment...

In your Oqtane installation (latest dev branch code), please comment out the StreamRendering attribute in Oqtane.Client\UI\Routes.razor

and run the framework to see what result is produced. In my local environment I get:

[krishnavsr]

@sbwalker
It continues to work fine for me with that commented out

[sbwalker]

More strange behavior... I just updated my local environment to VS 17.8.7 and reinstalled the .NET SDK 8.0.3... and now the Oqtane Framework will not compile:

Severity	Code	Description	Project	File	Line	Suppression State
Warning	CS9057	The analyzer assembly 'C:\Program Files\dotnet\sdk\8.0.203\Sdks\Microsoft.NET.Sdk.Razor\source-generators\Microsoft.CodeAnalysis.Razor.Compiler.SourceGenerators.dll' references version '4.9.0.0' of the compiler, which is newer than the currently running version '4.8.0.0'.	Oqtane.Client	C:\Source\Projects\oqtane.framework\Oqtane.Client\CSC	1	Active

[oqtanecms]

just updated my local environment to VS 17.9.5 and the .NET SDK 8.0.2.The framework with latest dev branch code compiles without problems:

It runs without any problem:

[thabaum]

@sbwalker dev branch can now be updated to version 5.1.1 for reporting issues. I can build and run Oqtane in Visual Studio with the latest updates. I have not had time to test SSR issue requested yet.

[mdmontesinos]

I just tested the lastest dev branch by commenting the StreamRendering in Routes.razor and it works perfectly fine. All the content is displayed without any problem.

[sbwalker]

Thank you everyone for your assistance. I believe the differences in behavior are related to the different SDK versions that people have installed. I was told by a source at Microsoft that Blazor in .NET 8 “came in hot” meaning that it had to ship by a certain date even if it wasn’t 100% ready. This means that the patch releases of .NET 8 (8.0.1, 8.0.2, 8.0.3) contain a lot of critical fixes to mainline use cases. Which explains the unexpected behavior we saw early in the Oqtane integration versus now. Also, when the package dependencies are updated in a .NET solution to a newer patch version it does not mean your development environment is going to benefit from them unless you also install the related SDK. In my case I was still developing on an older SDK version even though Oqtane was updated to .NET 8.0.3 packages (and I noticed that many of you are also not fully updated to the 8.0.3 SDK).

[thabaum]

@sbwalker I install the latest hosting bundle.

https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-aspnetcore-8.0.3-windows-hosting-bundle-installer

ASP.NET Core Hosting Bundle contains everything you need to run existing web/ server apps. The bundle includes the .NET runtime, the ASP.NET Core runtime, and if installed on a machine with IIS it will also add the ASP.NET Core IIS Module. If you only want the .NET or ASP.NET Core runtime, you'll find them in .NET 8.0 Downloads.

[sbwalker]

I just did a build from the Dev branch and deployed it to Azure and it runs fine. When I use Kudu to check which version of the SDK it is running it says:

C:\home>dotnet --info
.NET SDK:
Version: 8.0.101
Commit: 6eceda187b
Workload version: 8.0.100-manifests.69afb982

So it appears that Azure is a couple of SDK patch releases behind - and I am not aware of any way to update it in an App Service. Regardless, Oqtane is working fine on 8.0.1 so its not really an issue.

[thabaum]

@sbwalker maybe you can set it manually in azure with command line?
https://learn.microsoft.com/en-us/azure/app-service/configure-language-dotnetcore?pivots=platform-windows#set-net-core-version

dotnet --info
.NET SDK:
 Version:           8.0.203
 Commit:            5e1ceea679
 Workload version:  8.0.200-manifests.a7f084b6

Host:
  Version:      8.0.3
  Architecture: x64
  Commit:       9f4b1f5d66

[sbwalker]

its work on 8.0.1 so its not really an issue

[thabaum]

After todays update:

 dotnet --info
.NET SDK:
   Version:           8.0.204
   Commit:            c338c7548c
   Workload version:  8.0.200-manifests.8f02a06a

Host:
  Version:      8.0.4
  Architecture: x64
  Commit:       2d7eea2529

Just curious if you need to restart the app service or do something in Azure to update to latest. I do not currently have an account to test. I also wonder if you moved it's location if it would use the latest since it may move things to a server with the newer version? Then maybe move it back to it's original location to see if can get on a server running the latest version at that hosting location... just thinking out loud a little.

Seems like Azure should always be the latest.