.Net 6 and Autodesk product plugins

[soonhui]

As of Autodesk product version 2023, the .Net framework used by the assemblies that are referenced by plugin is .Net framework 4.7. I wonder if ( or when) Autodesk is going to transit to .Net 6 and higher. 

.Net framework 4.8 is the last release. From then onwards, all the .Net improvement will be carried on in .Net 6, 7 and onwards ( which is built on the code base of .Net core instead of .Net framework).

The problem is that .Net 6 codebase is not exactly the same as .Net framework, and so .Net 6 assemblies can't consume .Net framework 4.8 assemblies ( unlike .Net framework 4.8 dlls can use .Net 4.0 dlls). So as a Windows application developer and Autodesk plugin developer, we need to ensure that when we transit to .Net 6, all our applications and plugins are on the same page, which means that by then Autodesk plugins must be .Net 6 ready.

If Autodesk suddenly transits to .Net 6 while our main applications are still stuck at .Net framework 4.8, that will mean that all our Autodesk plugins will break and we can't fix them in a short time, this will impact our customers and our bottom line. Autodesk can't keep silence on this because the transition from .Net framework to .Net is a huge undertaking, and which requires planning and man month for testing.

We will appreciate if Autodesk can give us some kind of roadmaps. 

[m.buehler1]

I asked this Autodesk support many times... unfortunate still no roadmap. I hope that .NET 6+ will not appear one day in a Autodesk release candidate without previous announcement, preferable some months ahead.

For our company the migration of WCF and WF which Microsoft removed from .NET6+ requires several months of developer work.