Dynamics Community Forum Thread Details

.Net development and X++ development

I'm trying to get a connection to Azure Service Bus to work from X++.

I actually do have it working, but I'm getting these warnings in VS: (cut down for brevity)

Found conflicts between different versions of the same dependent assembly. In Visual Studio, double-click this warning (or select it and press Enter) to fix the conflicts; otherwise, add the following binding redirects to the "runtime" node in the application configuration file: <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Threading.Tasks.Extensions" culture="neutral" publicKeyToken="cc7b13ffcd2ddd51" /><bindingRedirect oldVersion="0.0.0.0-4.2.0.1" newVersion="4.2.0.1" /></dependentAssembly></assemblyBinding>

This is what I did:

New D365 F&O project
Updated the project file to set the .net version to 4.7.2
Add a .Net Framework Class Library project to the solution. Target framework 4.7.2
Add the following Nuget packages:
- Azure.Core (1.20.0)
- Azure.Identity (1.5.0)
- Azure.Messaging.ServiceBus (7.12.0)

The code works, but it gives the above warning and I;m worried that this might cause problems down the road or during runtime on a tier2/production environment.

It says to update the app.config with those mappings, but there is no app.config for an X++ project, not does it let you add one.

Any ideas?

Quick Links

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL