StudioElf SyncFusion and Module Compatibility

[bvillers-jr]

I just installed the StudioElf SyncFusion components only to discover that that module template generates code for .Net 8, not .Net9, which is used by the latest version of Oqtane at the time of this writing. While installing the StudioElf module, nothing in the UI at that time indicated that I was installing a module designed for an older version of Oqtane.

If this were a typical user-facing module it would be a poor user experience at best.

This leads me to wonder:

-Was this module simply created with a compatibility of 'Latest Version' or is the framework not handling this?

-What are best practices with regard to using 'Latest Version'?

[leigh-pointer]

@bvillers-jr Thanks for the comments. I isn't possible at this moment to couple a template with a particular version of the framework. However with the latest release of the SyncFusion templates - released 20-Jan-2025, I have given some feedback in the Oqtane Module and Theme creation areas.

Module:

Theme:

[patrickjlee]

Thanks @leigh-pointer - does that mean that the new templates work with .NET 9 ? (NB I had a similar problem with the templates being for .NET 8 a few weeks ago and tried to report it on the Studio-Elf website, but I don't think the "report a problem" form works properly - at least I never got any follow up).

[leigh-pointer]

@patrickjlee The MudBlazor 8 templates were released for Oqtane 6 targeting .net9.0 Unfortunately, not with this visual update.

[bvillers-jr]

I tried Studio-Elf Templates Syncfusion 28.1.39 which seems to be made for .Net 9. It did not go well. It creates the module code but it isn't able to successfully build. I'm sharing what I've learned so far here in case it helps someone else:

1- Content of the Manager class in the server project is duplicated. The using statements and entire class are duplicated in that file.

2- Manager class in server project is missing several using statements (using System; / using Oqtane.Interfaces; / using System.Threading.Tasks;) There is also a code error causing it not to compile.

3- The debug.cmd file is wanting to: XCOPY "..\Client\bin\Debug%TargetFramework%\System.IO.Pipelines.dll" "....\oqtane.framework\Oqtane.Server\bin\Debug%TargetFramework%" /Y
However, that file isn't output by the client project so I added a REM statement ahead of it to ignore that line. Not sure if this is the right thing to do or if something needs added to the client project.

4-Client project is set as the default startup project. Presumably this should be the Oqtane.Server project?

At this point I can successfully build the project!

However, when I run the Oqtane.Server project by setting it to startup project and clicking the IIS Express play button, it starts up Oqtane, but the new module with SyncFusion capability isn't there to be added to a page.