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
Describe the bug MetadataGenerator365.exe and MetadataGenerator365.exe.config is not added to the Metadata folder when using the "new" project file structure.
To Reproduce
Steps to reproduce the behavior:
Create a new empty solution.
Create new test project using the "new" project file structure.
Not Metadata folder is generated.
Expected behavior Metadata folder is generated with MetadataGenerator365.exe and MetadataGenerator365.exe.config.
Screenshots
Environment
Windows 11
Tool version: 1.12.3
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 and MetadataGenerator365.exe.config to the manually created Metadata folder, the tool throws this exception:
.\MetadataGenerator365.exe
Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'Microsoft.Xrm.Sdk, Version=9.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Invalid pointer (Exception from HRESULT: 0x80004003 (E_POINTER)) ---> System.NullReferenceException: Object reference not set to an instance of an object.
at DG.Tools.XrmMockup.Metadata.AssemblyGetter.GetAssemblyFromName(String Name)
at DG.Tools.XrmMockup.Metadata.Program.ResolveXrmAssemblies(Object sender, ResolveEventArgs args)
at System.AppDomain.OnAssemblyResolveEvent(RuntimeAssembly assembly, String assemblyFullName)
--- End of inner exception stack trace ---
at DG.Tools.XrmMockup.Metadata.Program.GenerateMetadata()
at DG.Tools.XrmMockup.Metadata.Program.Main(String[] args)
This is resolved by copying the Microsoft.* assemblies from bin/Release/net462 to the Metadata 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:
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: