-
Notifications
You must be signed in to change notification settings - Fork 28
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
New project structure does not support metadata from D365 instance. #233
Comments
And I did add this "hack":
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
MetadataGenerator365.exe
andMetadataGenerator365.exe.config
is not added to theMetadata
folder when using the "new" project file structure.To Reproduce
Steps to reproduce the behavior:
Not
Metadata
folder is generated.Expected behavior
Metadata
folder is generated withMetadataGenerator365.exe
andMetadataGenerator365.exe.config
.Screenshots
Environment
Additional context
This is not using the
XrmFramework
project structure due to using XrmToolkit ofr plugin registration and "metadata" generating.When moving the
MetadataGenerator365.exe
andMetadataGenerator365.exe.config
to the manually createdMetadata
folder, the tool throws this exception:This is resolved by copying the
Microsoft.*
assemblies frombin/Release/net462
to theMetadata
folder. It might be related, it might not or it might be me doing something wrong :|The text was updated successfully, but these errors were encountered: