How do I reference a .dll in an X++ class in D365?

(0) Share

Report

Posted on by Wmyk

152

I feel like I'm missing something obvious, but I took a .dll SDK and added it as a reference to my project and created an X++ class. I added "using" lines at the top of the class, but I'm getting "A reference to 'xxx' is required to compile this module."

Autocomplete is detecting the class and providing suggestions. What am I missing? See image below:

Categories:

Development / Customization / SDK

All responses (7)

Answers (2)

Sort by

Verified answer

Jie G Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi Wmyk,

You still need to add reference to netstandard, which the sdk is referenced to.

Please check the Version of .Net framework in your system, you can check in VS: Help -> About Microsoft Visual Studio.

The SDK dll might be built on higher verison of .Net, and the netstandard comes inbox starting from .Net 4.7.1, so you may need to upgrade your .Net framework.
Wmyk 152 on at

Like (0)

Report
Copy link

Link copied!

I have the same version of .Net as your picture. How can I check if the SDK dll is on a higher .Net version? It's for a D365 environment, so is upgrading my .Net version feasible given that it could eventually be on a production machine?

Is there an actual "netstandard" reference, like "System" or "System.Core" that I need to add? I'm newer to .Net dev if that's not obvious.
Wmyk 152 on at

Like (0)

Report
Copy link

Link copied!

I have access to the SDK source and it looks like there's a ".NETStandard 2.0" dependency.

I just took the assembly because the source seemed to only work on VS2017 and not VS2015.

Do the D365 VM's not support .Net Core? Or can I convert the SDK to .Net Standard?
Verified answer

Martin Dráb 240,845 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

D365FO isn't a .NET Core application. The VM surely can host .NET Core application, but that's not going to help you.

Anyway, it seems that you've picked a wrong build of the SDK. It compiles just fine for me with the one for .NET 4.0. (I've downloaded the NuGet package, unzipped it and took the file from lib\net40).
Wmyk 152 on at

Like (0)

Report
Copy link

Link copied!

Since I can't use NuGet on D365, I took the source from GitHub, compiled it, took the version in bin\net40 and it didn't work for me. I didn't realize I could just download/unzip a NuGet package.

I changed the .csproj "<TargetFramework>" to only target "net40" and removed the other two and recompiled, then took the new DLL and it worked for me. I have no idea?
Jie G Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi Wmyk,

Can you find this dll in your VM? You can tried to add reference to it and compile again.

Please refer this known issue: github.com/.../542
Wmyk 152 on at

Like (0)

Report
Copy link

Link copied!

I have that folder, but that DLL is not there.

It seemed like that issue is when compiling it in VS 2017, it targeted the 3 different frameworks for output, and somehow the net40 file still had references to netstandard. When I changed the .csproj as pictured above and re-compiled it, it worked.

And the D3FO machines do not support .Net Standard (I think)?