microsoft / microsoft/Dynamics365Commerce.Solutions

NuGet Packages are not referencing Properly in Retail SDK to Commerce SDK Migration

Open
#248 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Other Development Issue

Summary

Describe the issue
We have done Migration of this code below shown in Screen Shots. In this migration we are facing this error were we have two NuGet package reference which is not working properly. As well as the code i have given below uses the NuGet Package from Retail and it gives me error regarding the code does not exists in current context. So how will we reference this NuGet package related error's.

Version and Error Info
Commerce SDK Version: 9.44

Screenshots.

The NuGet Packages directives which I'm using is in this screen shot.
image

The error I'm getting in the code block is given below Screen Shot.
image

These are the error shown in the error list.
image

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 reviewing the NuGet package directives and migration code shown in the issue screenshots, using Commerce SDK 9.44 as the reproduction context. Reproduce the unresolved references and determine which package references are required; done means the migrated code resolves its referenced types without the reported errors.

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.