I'm trying to follow the directions here (Factory Default Widget Providers) and here (Managing Widget Source and Distribution) and I'm having an issue where if my class implements IScriptedContentFragmentFactoryDefaultProvider it will not show up in the list of Extensions and therefore I can't enable it to use as a Factory Default Provide when creating new widgets in Developer Mode.
public class SampleWidgetProvider : /* IPlugin */ IScriptedContentFragmentFactoryDefaultProvider
{
#region IScriptedContentFragmentFactoryDefaultProvider Members
private readonly Guid _identifier = new Guid("b740a034-c218-458d-b094-23e1f913cff0");
public Guid ScriptedContentFragmentFactoryDefaultIdentifier
{
get { return _identifier; }
}
#endregion
#region IPlugin Members
public string Description
{
get { return "Factory provider for sample widgets"; }
}
public void Initialize()
{
}
public string Name
{
get { return "Sample Widget Provider"; }
}
#endregion
}
If I comment out the implementation implements IScriptedContentFragmentFactoryDefaultProvider and just have the class implement IPlugin, it shows up.
When I attach a debugger to w3wp.exe, I hit the constructor breakpoint for the plugin when it only implements IPlugin. If I then recompile and deploy the file implementing only IScriptedContentFragmentFactoryDefaultProvider and reattach the debugger, I can also hit the constructor breakpoint and even enable the plugin provided that I never refreshed the Extensions page. Then it shows up as a Default Factory Provider when I try to create a new widget in Widget Studio. Weird, huh?
I'm using Community version 11.1.0.9731. That's the version included in the downloadable package (from May 20) when requesting a trial version of the community. The DLL is compiled as Debug against .Net Framework 4.7.1.
Sorry for peppering with all the questions, but I need to get spun up on this quickly to determine if Telligent is a platform we can migrate a large, complex community to and I need to test out all the functionality.
