pyRevit 5

[eirannejad]

Priority 1:

• branches: main-4 and develop-4 for pyRevit 4* and main and develop for pyRevit 5 @eirannejad
• support for netcore (try to keep compatibility with netfx - maybe compile pyRevit to netstandard2) @dosymep
• performance: pyrevit dotnet runtime no longer to compile at Revit launch @eirannejad

bin/
bin/netfx/
bin/netfx/engines
bin/netcore/
bin/netcore/engines
bin/pyrevit.exe <- `netcore`

• purge old ironpython engines @sanzoghenzo

Priority 2:

• performance: faster extension parsing (dotnet extension) (Bundler library)
• performance: rewrite ui builder in dotnet so it is faster

[eirannejad]

@jmcouffin @sanzoghenzo @dosymep

https://discourse.pyrevitlabs.io/t/invitation-to-pyrevit-meetup-2-12th-february-4-30pm-cet/2640/5?u=eirannejad

@dosymep
I also moved all the pyrevitlib/pyrevit/runtime/*.cs files into dev/pyRevitLabs.PyRevit.Runtime. We need to:

• setup pyRevitLabs.PyRevit.Runtime to build these csharp files into netstandard
• setup pyrevitlib/pyrevit/runtime/__init__.py to not compile these files anymore and just load the assembly and provide access to the types

[dosymep]

@eirannejad, I created draft-pr #2088

[jmcouffin]

I just fixed dependabot to work against the develop-4 branch for now

[jmcouffin]

RevitNet8UpgradeTips.pdf
for reference

[jmcouffin]

For reference, assembly load contexts
https://docs.microsoft.com/dotnet/api/system.runtime.loader.assemblyloadcontext

A way to prevent Dll conflicts that is partially implemented in some edge cases in dynamo

https://devblogs.microsoft.com/powershell/resolving-powershell-module-assembly-dependency-conflicts/

[jmcouffin]

further reference jeremytammik/RevitLookup#210

[jmcouffin]

#2088 for reference to ilpack.

[jmcouffin]

for reference, pages 20+ and pages 35+ https://thebuildingcoder.typepad.com/files/migrating_to_net_core_8_webinar.pdf

and

https://thebuildingcoder.typepad.com/files/migrating_to_net_core_8.pdf

[jmcouffin]

for reference
chuongmep/RevitAddInManager#54

[github-actions]

"👋 Hi there! It looks like there hasn't been any activity on this issue for the past 60 days. We understand that things can get busy.
Just a friendly reminder that this issue is scheduled to be automatically closed in 14 days if there's no further activity.
If you still need assistance or have additional information to share, please feel free to comment, and we'll be happy to help! 🚀
Thanks for your understanding!"