All of the major pieces are on our Dynamo Public Roadmap - including the .NET 6.0 work that I just put up. Sometimes, things come up swiftly that may not show up here but generally you can rely on this for the work being done, or planned.
2 Likes
The Python engine change and the lack of the Package Manager supporting versions for specific versions of Revit have made Dynamo extremely undesirable to develop a custom package for anymore.
6 Likes
I really do for my package it In 2021, but now it really came Dynamo in 2023 
I t’s nothing new to me but I’m sure it will save more time for other authors to create good scripts.
3 Likes
Pretty sure. Everything will change to some degree, but the specifics of the impact on Python tools aren’t clear at this time. Might make CPython more stable.
I think it’s safe to assume this includes existing add-ins for Revit/AutoCAD/Civil3D/etc…
To be confirmed, but, this means that you probably need to update the python engines, because not all of them support .Net 6 (compatibility)
| Current Python engine version | → | Compatibility .Net Core 6, need to upgrade to ? |
|---|---|---|
| IronPython 2.7.9 | → | IronPython 2.7.12 (target .NET Standard or .Net 6?) |
| IronPython 3.4 | → | seem ok |
| PythonNet 2.5.2 | → | PythonNet 3.0.x (target .NET Standard or .Net 6?) |
1 Like
@Anton_Huizinga The Civil 3D team has added .NET 6.0 upgrade to their roadmap now: https://portal.productboard.com/jepvxreqkffwuku66cnkvxke/c/429-upgrade-civil-3d-and-its-extensions-to-net-6-0?utm_medium=social&utm_source=portal_share
2 Likes
Ah, thanks for the information Sol 
We will investigate the impact on our developments in the company and create a plan to update our plug-ins. Unfortunately the Arkance Systems Node Library will be the last development item on the list, but I hope I will have finish it when Dynamo v3 is out.
4 Likes
And Revit’s roadmap card: https://portal.productboard.com/aec-bid/7-architecture-revit-public-roadmap/c/397-revit-to-net-6-or-higher?utm_medium=social&utm_source=portal_share
5 Likes
For all developer from now, I think .net standard is good to start now 
.NET Standard | Microsoft Learn
2 Likes
Not really, .NET Standard is just an old version that was available aside from .NET Framework. The same with .NET Core. Now it is just .NET 6 (and 7 and 8).
Microsoft does not really have a great reputation with naming 
4 Likes
I have carefully reviewed all the comments in this thread, and I understand that implementing the proposed change might be challenging. To approach this pragmatically, I have three questions aimed at minimizing the effort required:
- What are the advantages we can expect to gain from this upgrade?
- What steps should we take now until the new update arrives? Specifically, what do we need to learn and how can we test .NET Core?
- Once the .NET release is available, what are the steps we need to follow to upgrade our package?
In addition, I hope the Autodesk team can provide us with a roadmap on how to upgrade our packags.
Hi @RMohareb - some aswers inline below
The most important one is that if we don’t do it, Dynamo will no longer work in Revit and Civil 3D as we all have to be targeting the same framework. Beyond that, you can expect a large performance boost, modernized approaches to improve developer productivity, and better tooling.
Until Dynamo has a build that is on .NET 6 the only action be taken would be to be aware of it, and plan around it. As soon as we have a working daily-build we will be blasting that out with our technical blog post explaining in a lot more detail what’s changed, and what package authors need to do, and should be aware of.
We will be putting out a technical blog post on the .NET 6 upgrade, and also directly contacting package authors who will be affected.
5 Likes
Though not publicly, but it has now been confirmed by Autodesk that AutoCAD 2025 will target .NET 8. The current Alpha uses .NET 6 but the Beta and Final release will use .NET 8.
Fortunately the AutoCAD API has not changed, but the challenge for us are the changes in .NET itself.
1 Like
Thats great news. Do you know why are they not upgrading AutoCAD to CORE 8?
There is no Core. Or there is, depends on your view on things
Since .NET 5 there is just .NET, no Core, no Standard and no Framework.
1 Like
Apologies for the confusion @Anton_Huizinga, I meant to say do you know why they’re not upgrading AutoCAD to .NET 8?
1 Like
I am not sure if I misunderstand, but Autodesk is targetting AutoCAD 2025 to .NET 8. And therefore Civil 3D too, and therefore Dynamo too.
1 Like
Thanks for clarifying. Thats awesome news. I thought when you said AutoCAD API has not changed, you meant AutoCAD was sticking with .NET Framework!
2 Likes