Open thygesteffensen opened 4 months ago
And I did add this "hack":
<!-- This ItemGroup is only here because the assembly getter in XrmMockup is stupid -->
<ItemGroup>
<Reference Include="Microsoft.Xrm.Sdk, Version=9.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL">
<HintPath>bin\Release\net462\Microsoft.Xrm.Sdk.dll</HintPath>
</Reference>
<Reference Include="Microsoft.Xrm.Tooling.Connector, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL">
<HintPath>bin\Release\net462\Microsoft.Xrm.Tooling.Connector.dll</HintPath>
</Reference>
<Reference Include="Microsoft.IdentityModel.Clients.ActiveDirectory, Version=3.19.8.16603, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL">
<HintPath>bin\Release\net462\Microsoft.IdentityModel.Clients.ActiveDirectory.dll</HintPath>
</Reference>
<Reference Include="Microsoft.Crm.Sdk.Proxy, Version=9.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL">
<HintPath>bin\Release\net462\Microsoft.Crm.Sdk.Proxy.dll</HintPath>
</Reference>
</ItemGroup>
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 :|