Hello @Tiwana, Ramandeep ,
Thank you for sharing.
I cannot confirm Retail Realm's own packaging plans, but from the .NET/NuGet side, a package that only ships a net6.0 target is not a direct fit for a project that must stay on netstandard2.0.
NuGet selects package assets based on the target framework of the consuming project. If the Retail Realm package only contains net6.0 assets, NuGet has no compatible asset to use for a netstandard2.0 project.
The important distinction is that netstandard2.0 is a compatibility target used to share library code across supported .NET implementations, while net6.0 is a modern .NET target. Microsoft’s .NET Standard guidance states that .NET 5 and later reduce the need for .NET Standard in most scenarios, but if a library needs to share code between .NET Framework and other .NET implementations, netstandard2.0 is the recommended target.
You can see the references here:
If your project must remain on netstandard2.0, the practical next step is to ask the Retail Realm package owner whether they can publish a compatible netstandard2.0 asset, or a multi-targeted package that includes both net6.0 and netstandard2.0, if their code can support that.
If the package owner only provides net6.0, then the consuming project/application would need to retarget to a compatible modern .NET target, or you would need to use an older package version that still contains compatible assets.
I hope this helps. If you found my response helpful or informative, I would greatly appreciate it if you could follow this guidance or provide feedback.
Thank you.