[Task]: New C# Loader Testing

[jmcouffin]

Task

• Main issue to centralized notes and test around the new C# Loader

• Test with CPython engine

Notes

• The new loader requires a Revit restart when:
  • it is switched on or off
  • language of the pyRevit UI is changed
  • python Engine is changed

[jmcouffin]

@Wurschdhaud
@tay0thman
@MohamedAsli

Can you give it a ride and try and break it using the latest WIP installers?

Please open specific sub-issues when relevant.
If it is something very small, just add it directly in here.

[tay0thman]

I'm on it, starting with my old benchmark, let's see improvements as well as any bugs, crashes, I have toolbars linked from everywhere (ACC, Corporate Network with VPN....etc.)

running 5.3.1.25348 from pre-Christmas era.

AFTER updating to 5.3.1.26008 from Today, I see a sizable speed improvement

After Removing some of the weird Extensions:

[jmcouffin]

I see a sizable speed improvement

One thing to know about, I saw that timing improved after a few restart. New loader + Revit accelerator caching I'm guessing.

[tay0thman]

@jmcouffin added 2 sub-issues, I think they are related to the issue #2995 which is the main issue when the loader requires a complete restart of revit to get the extensions updated.
Next I will test the cpython modules with it.

[jonatanjacobsson]

im testing it out aswell, found that extension scripts that need pyrevit cannot use 'engine: clean: true' in the bundle, because the pyrevit module isn't re-injected into the path after the engine is cleared. This could bundle.yaml like this: bundle.yaml
I dont know if this is the indended behavior or not however :)