Hi,
We've just had to make a change to our live system because the Radzen HTML component seems to have disappeared. We're on the latest version always because we use *. Has this not been removed? It's fine, we've replaced it with our own component, but I was just concerned that this could happen again without us being aware that that change is being made to our component library,
Thanks,
Colin.
Hi Colin,
RadzenHtml was removed in v11.0.0. It was one of our oldest components and did almost nothing on its own - its whole implementation was just:
@if (Visible)
{
@ChildContent
}
So the replacement is usually to delete the wrapper and keep the content inside it. If you were relying on the Visible toggle, a plain @if (or a if you needed an element) does the same job:
@if (visible)
{
@* ...your content... *@
}
On the notification point - this went out in a major release (10 -> 11), which is where we reserve breaking changes per semver. Since you reference the package with a wildcard, you were rolled onto v11 automatically. If you'd like to avoid surprise breaks like this, I'd recommend pinning to a specific minor version (e.g. 10.4.*) and upgrading major versions deliberately after reviewing the release notes. We'll also make sure component removals are called out clearly in the v11 release/migration notes.
Sorry for the disruption, and glad you already have a working replacement.
Yes thanks for that. That's what we've done: we've just put in something to mimic its behaviour so that's all good.
Yes we've done that on our live server. We now we're going to point at a particular version until we've checked that we're happy in our testing and dev environments.
I don't know if you remember but a long time ago I've been working on upgrading our Radzen components, which took a long time because we didn't realise we were working on a very old version but we finished that project and went live. We're on the latest versions of.NET and Radzen and everything else so this is just something that wasn't on our radar but thank you very much for the quick response and yeah everything is working perfectly, thank you.