Inheriting from Telligent.Evolution.Extensibility.UI.Version2.ConfigurableContentFragmentBase

I can replicate this, and I’ve logged it as TE-19704. There is no workaround at this time.

As you’ve probably noticed, the NuGet-hosted package referenced by plugin projects, Verint.Community.Platform, includes only a single assembly: Telligent.Evolution.Platform. This is not the same Telligent.Evolution.Platform assembly included in the actual application. Instead, it contains empty, generated proxy types that match the signatures of API and extensibility types from multiple assemblies in the actual platform. It excludes implementations, as well as other types that are not part of the API.

You’ve identified an edge case in the tool that generates this proxy package, as ConfigurableContentFragmentBase has some unusual characteristics. This has been logged for correction.

However, I should note that the triage decision for this particular issue may be to remove ConfigurableContentFragmentBasefrom the API instead. It may have been included accidentally.

Can you share your use case for it?

I can replicate this, and I’ve logged it as TE-19704. There is no workaround at this time.

As you’ve probably noticed, the NuGet-hosted package referenced by plugin projects, Verint.Community.Platform, includes only a single assembly: Telligent.Evolution.Platform. This is not the same Telligent.Evolution.Platform assembly included in the actual application. Instead, it contains empty, generated proxy types that match the signatures of API and extensibility types from multiple assemblies in the actual platform. It excludes implementations, as well as other types that are not part of the API.

You’ve identified an edge case in the tool that generates this proxy package, as ConfigurableContentFragmentBase has some unusual characteristics. This has been logged for correction.

However, I should note that the triage decision for this particular issue may be to remove ConfigurableContentFragmentBasefrom the API instead. It may have been included accidentally.

Can you share your use case for it?

It is used on about 10 different customer sites and is part of the InlineContent Extension.

To enable us to continue I have a solution, but the technique is not exactly supported :) 

I understand you use it. I’m just trying to understand its use from a technical perspective versus a scripted alternative.

I'll send you the current source if you want?

I am trying to also remind myself how it works and why, it has been around a long time. 

The inline content works in 2 parts the first part is inherited from ConfigurableContentFragmentBase, this is the widget that is embedded on the page.  It can't be a standard scripted fragment widget because it has features that are not supported in those widgets.

Even with my workaround for the abstract properties, I assume the FindTypes and associated constructor can't be invoked because the base class has private types, but you would know more than me. 

When this widget renders on the page it uses its information to and a IScriptedPanel to render the content. 

TLDR; It's pretty important to keep supporting this API type.

Can you please provide what features you are referring to and why they are not capable of being done in another way?

Happy to share the code and you can give advice on how to support it.

That would be helpful, along with a brief functional expalanation

Michael Monteleone said:

I’ve logged it as TE-19704.

I'm looking at getting the reference type representation of ConfigurableContentFragmentBase corrected with TE-19704. It may still be deprecated in the future though.