You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following #916 changes, it seems that one might face a problem when using dotnetcore2 and pyaedt.
Indeed, pyaedt has it's own clr_module and loads dotnetcore2 before pyedb does. Therefore, DOTNET_ROOT is set to the python environment dotnetcore2 location. This is a problem since the current implementation leads to loading a configuration file that isn't present.
Steps To Reproduce
Which Operating System are you using?
Windows
Which Python version are you using?
3.10
Installed packages
Not relevant
The text was updated successfully, but these errors were encountered:
Before submitting the issue
Description of the bug
Following #916 changes, it seems that one might face a problem when using dotnetcore2 and pyaedt.
Indeed, pyaedt has it's own clr_module and loads dotnetcore2 before pyedb does. Therefore, DOTNET_ROOT is set to the python environment dotnetcore2 location. This is a problem since the current implementation leads to loading a configuration file that isn't present.
Steps To Reproduce
Which Operating System are you using?
Windows
Which Python version are you using?
3.10
Installed packages
Not relevant
The text was updated successfully, but these errors were encountered: