microsoft / microsoft/Dynamics365Commerce.Solutions

How to distribute Payment connectors with new commerce SDK install solution [ScaleUnit.Sample.Installer]

Open
#273 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
80
Forks
38
No merged PRs in 30d

Description

Build Issue

Summary

I am unable to include the payment connector files to the extension installer.

I have followed the solution of this issue https://github.com/microsoft/Dynamics365Commerce.Solutions/discussions/176

and are able to to have the payment connector files included in the scale unit deployment package by including

<ItemGroup>
  <IPayment_Processor_Assemblies Include="path to dll">
    <CopyToOutputDirectory>Always</CopyToOutputDirectory>
  </IPayment_Processor_Assemblies>
</ItemGroup>

in scaleUnit.csproj file.

This does not solve the issue for the scaleUnit.Sample.Installer. I have also tried using Content include

<ItemGroup>
  <Content Include="path to dll">
    <CopyToOutputDirectory>Always</CopyToOutputDirectory>
  </IPayment_Processor_Assemblies>
</ItemGroup>

without any success, and also tried to add project reference

Version and Error Info

Commerce SDK Version: 9.47

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the ItemGroup entries in scaleUnit.csproj with the packaging behavior of scaleUnit.Sample.Installer. Verify whether the payment connector DLLs appear in the extension installer output, and consider the issue complete only when the installer includes them; the issue provides no named test or further entry point.

Written by the indexing model from the issue text.

Assessment

Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.