More fun to come
3 Likes
How hard this time going from Netcore 8 to 10? I assume it is minimal.
If we need to keep the installers and the code base compatible with previous versions _ which we do, because cli, clones, ā¦, Iād say, probably a monthā¦(Full-time)
I tried, a quick and dirty upgrade, myself when I heard the news, didnāt work that fast. A nice Rabbit hole to get in 
to debug.
1 Like
Sounds good! Iāll free up myself for some testing as well.
Thank you @Jean-Marc
What are the steps involved to upgrade pyRevit? Iām curious about the technical āstuffā that goes into a polished pyRevit release for a new .NET version. I know this was a big undertaking for the 2025 release.
Read:
Also taie. A look at the commits and files changed.
The main issue was to structure the automatic switch and the folders organization.
Now, high level plan:
- new Ā·net10 CI (it will take longer until we get Autodesk to actually make all supported Revit to that version)
- new folder location
- copy to new folder system
- test
- fix in an infinite loop
Something to add @sanzoghenzo ?
2 Likes
Sorry I didnāt get the notificationā¦
Hereās what we need to watch out for:
Does the last sentence in the Autodesk communication mean that they will also upgrade revit 2025 and 2026 to .net 10? If so, it is just a matter of changing the compilation target from net8 to net10 and fix the breaking changes
1 Like
This is in the plans, I confirmed with them. Ill give it a try over the coming holidays.
Obviously, I had to try again.
Well, an hour later, not that simpleā¦
1 Like
@Jean-Marc do you have a link to whatever roadmap this is from? Missed the OP when it came out/havenāt seen this yet
Autodesk website, Revit roadmapā¦