Shaun Walker

@MackinnonBuck the fact that you were not able to reproduce the problem prompted me to do some further investigation... I started the Oqtane migration to use the new .NET 8...

@MackinnonBuck the current guidance you linked to is quite thorough. The only scenario which is not mentioned is that enabling StreamRendering can cause unexpected "The renderer does not have a...

Spoke too soon... the Azure site where I deployed the bits with StreamRendering removed is still not rendering content in some scenarios:  So I am guessing that SDK 8.0.1...

Upgraded my Azure App Service to .NET SDK 8.0.4 (using Development Tools / Extensions) and the rendering problem is resolved.

I realize that I did not provide a minimal repro - however the scenario is very easy to replicate. Basically create a shared razor component which contains an image tag....

@Eilon the GetAssetUrl() suggestion is exactly what I am doing in Oqtane already... but it feels like the wrong approach to treat this as a development concern (by forcing it...

The ability to have razor components work seamlessly across ALL hosting models is definitely something that clients want. In addition, they do not always want to take on the burden...

@Eilon is there any update on this item? The shared razor component story would be greatly improved by this remote resource reference capability. The Android Asset Pack/Play Asset Delivery (PAD)...

@mkArtakMSFT I am not sure I understand how #11382 relates to this issue. Basically, all I need is way to reference remote assets in my shared components (without having to...

When building component libraries one of the goals is to create components which function properly on all render modes. Further, it is highly beneficial if the component code does not...