Revit.TestRunner2025 - A Fork for Revit 2025

[beyerl]

Hi Tobias, hope this finds you well.

Since Revit.TestRunner has not been updated to .net8 and Revit 2025 yet, I have created a fork and performed the update myself. You can find it here: https://github.com/beyerl/Revit.TestRunner2025.

Since I wanted to keep things simple, I just performed the .net8 update on all projects and did not put emphasis on backward compatibility. Consequently my fork only works for Revit 2025, not for older versions.

I would be happy to start a merge request, but I guess, you will be aiming for a backward compatible solution. In that case, it is probably not a good idea to merge my fork. But it might still help with fixing some of the issues created by the update from .net framework 4.8 to .net8.

Also included are some convenience fixes like making the revit folder configurable with commandline arguments and deleting the automatic override of arguments when in debug mode.

If you have comments feel free to get in touch.

Best wishes, Lorenz

[tobiasfloescher-geberit]

Hi Lorenz,

Thanks for your message.

I have made a new version of Revit.TestRunner including support for Revit 2025. I used your implementation of the NUnitRunner class. It works fine when running from VisualStudio. But there seems to be a problem when the debugger is not attached. Revit wants to write an InternalTrace.log, but it is not allowed to write to C:\Program Files\Autodesk\Revit, obviously. But why this exactly happens, I haven't found out yet. Probably an AppDomain issue.

This is the reason why the new version of TR is marked as previous.

Unfortunately (as in the past) I have limited time to work on this. Do you have the same problem? If you have an idea, let me know.

After the holidays I will try to fix this problem.

Until then, all the best Tobias

[beyerl]

Hi Tobias,

Thanks for updating. I'm glad my NUnitRunner-Implemenation was useful to you. Unfortunately, my time to work on this project is also limited, but I'll see if I can have a look at the problem you mentioned next week.

On my fork, I haven't had the issue you are describing even when the debugger is not attached. For example, I'm using the TestRunner in an Azure Build Pipeline using a build agent on a windows VM and it works just fine.

Enjoy your holidays!

Best, Lorenz

[beyerl]

Hi Tobias,

I've had a minute to look at the current version. I cannot reproduce the InternalTrace.log error you are describing. However, I get a Platform not supported error when trying to load the SampleTestProject3-Assembly. Hope this helps.

Best, Lorenz