Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[pull] development from d365collaborative:development #99

Merged
merged 2 commits into from
Apr 11, 2024

Conversation

pull[bot]
Copy link

@pull pull bot commented Apr 10, 2024

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

rsteber and others added 2 commits April 8, 2024 17:50
If a module that is read by the disk metadata provider references a binary-only module, the "ListModulesInDependencyOrder()" method causes an exception error that is intercepted by the Get-D365Module function in line 172.
As a result, the order of the modules cannot be determined taking the dependencies into account and "ListModules" is used instead.
The problem can be easily avoided by adding the model manifest of the runtime metadata provider to the "CreateDiskProvider" method in line 165.

This ensures that the disk provider has all the information it needs to determine the sequence for all modules based on the dependencies.
…time-error

Disk provider binary-only module reference fix
@pull pull bot added the ⤵️ pull label Apr 10, 2024
@pull pull bot merged commit 7be7523 into FH-Inway:development Apr 11, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants