✨ Adds new function Publish-D365WebResources to simplify this process #871
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This pull request was automatically created by the d365fo.tools-Generate-Text action'
… the example directory does not exist
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I was recently bitten by the fact that web resources contained in resource objects in the AOT are not automatically deployed to the web resource folders when a module is retrieved from a version control repository.
This is a known issue, see https://www.yammer.com/dynamicsaxfeedbackprograms/#/Threads/show?threadId=555026298970112
While there is a workaround with scripts provided in deployable packages, it is cumbersome to use. Hence the new
Publish-D365WebResourcesfunction to make adding the missing resource files simpler.