Use section content for Splitter.Content() with RenderSection() .NET6

[Kevin]

I'm working in a migration to MVC .NET6 from .NET Framework, so in the Layout we use the following

@Html.Kendo().Splitter().Name("Splitter").Panes(p => {
  p.Add().Content(RenderSection("Header", true).ToHtmlString());
  p.Add().Content(RenderSection("Content", true).ToHtmlString());
});

As you can see we are using RenderSection() to take the HTML defined in other view. For each page we have the following code

But in .NET6 the same RenderSection() renders the content of the section. (has other behaviour)

There is other way to get the HTML from the sections?

 

Version: Telerik.UI.for.AspNet.Core.2020.2.513

MVC

[Alexander]

Hi Kevin,

I noticed that there is not a Telerik UI for ASP.NET Core license associated with your account which limits the availability of our support services for the product. In this regard, It is recommended that you either purchase or renew your license in order to gain access to the latest updates, fixes, features, and support regarding the Telerik UI for ASP.NET Core components. More information regarding the currently available plans can be reviewed here:

• Support Plans

With that being said, rendering the content of the Telerik UI for ASP.NET Core Splitter is not supported out-of-the-box. Having this in mind, if you wish to set the content of the panes, I would recommend using either of the options listed in the following documentation:

• Splitter Content Operations

Kind Regards,
Alexander
Progress Telerik

[Alexander]

Hi Kevin,

A duplicate of a support ticket relevant to the topic was opened recently where I have investigated the matter more thoroughly. I am posting my findings here so that members of the community can benefit from the information as well. 

"Upon further investigation, one possible approach would be to utilize the .Render() method to wrap the component declaration in a non-rendering code block with @{} instead of @(). Here is an example":

@{Html.Kendo().Splitter().Name("Splitter").Panes(p =>
	{
		p.Add().Content(@<text>@RenderSection("mySection", true)</text>);
		p.Add().Content(@<text>@RenderSection("mySection2", true)</text>);
	}).Render();
}

"With that being said, I cannot confirm with complete certainty whether the provided approach would have any future drawbacks. Nevertheless, here is a runnable sample that illustrates this approach in .NET 6."