fix: conflicting DLLs in Path variable #344
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @RobPasMue The issue arises from a version mismatch between the DLLs in the Ansys Python Manager and those required by Ansys Meshing Prime. The Ansys Python Manager's DLLs are being prioritized due to the inclusion of the Ansys Python Manager's _internal path in the system's Path variable. I have made the code changes to remove that path while launching command prompt and other applications.