Custom DLL on D365FO

(0) Share

Report

Posted on by Yuji

4,131

Hi,

Since standard D365FO x++ does not support encrypt/hash feature (e.g. Base64), we need to develop some custom feature in C# DLL. I remember I can do that in AX 2012, and deploy those DLLs on Server/bin folder. Is it still possible for this on D365FO, how do we deploy DLLs to the servers? How to include these DLLs in the deployable packages?

Thanks,

I have the same question (0)

All responses (9)

Answers (1)

Suggested answer

nmaenpaa 101,160 Moderator on at

Like (0)

Report

Yes, it's possible.

You put that DLL in the Bin folder of your package. Then add it as a Resource in AOT. Then add the Resource and the dll file to source control. Now your build process will include it in the deployable package.

Was this reply helpful? Yes No
Yuji 4,131 on at

Like (0)

Report

Thanks Nikolaos, to add the DLL to the resource in AOT, is it just for version control purpose?

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,160 Moderator on at

Like (0)

Report

No, you need to add it to Resources in AOT to be able to use it in your code.

Was this reply helpful? Yes No
Yuji 4,131 on at

Like (0)

Report

Hi Nikolaos,

I did find an article

community.dynamics.com/.../manage-your-references-to-net-assemblies-dynamics-365-for-operations-vs-projects

Is it similar to this?

Thanks,

Was this reply helpful? Yes No
Verified answer

nmaenpaa 101,160 Moderator on at

Like (0)

Report

Exactly this. And I meant Reference, not Resource, sorry for the confusion.

Was this reply helpful? Yes No
Yuji 4,131 on at

Like (0)

Report

Thank you very much Nikolaos!

Was this reply helpful? Yes No
Hugo Alves 129 on at

Like (0)

Report

Thank you guys for sharing...

We did exactly this way:
- Added DLL to: \OurModel\BIN\<CustomComponent>.dll
- Added Reference to: \OurModel\AxReference\<customcomponent>.xml

The problem now is that Reference Path property points out to Absolute FilePath,
which causes conflict among developers' branches and Main trunk:

- Developers in personal environment get their AOSPackage at C:
- Developers in LCS Cloud Hosted usually points out to K:
- Main trunk is also K:

Get Latest, Refresh models, Build, Errors... lots of errors
Any approach to reference Model\Bin\DLL with their Relative Path instead?

Thank you in advance.

Was this reply helpful? Yes No
Martin Dráb 237,880 Most Valuable Professional on at

Like (1)

Report

What errors are you getting?

I use a different workspace mapping paths then the rest of the team and I've never run into a problem. The bin folder of the packing is one of the probing paths, therefore if the file is there, it should work. The first thing to check is whether the file is in source control and whether the developers were able to download it.

An example I have here at the moment is using a project reference, not a DLL reference. The XML file of the reference doesn't contain any path at all, just Name, AssemblyName, AssemblyDisplayName and Version.

Was this reply helpful? Yes No
Hugo Alves 129 on at

Like (1)

Report

Just as Martin Drab said,
despite we see something like absolute path on Properties window of the Reference,
its XML file has no path at all. Perfect.

This answer proved the problem was not there, it made us double check
and indeed AxReference was not properly added to Source Control, Model\Bin\DLL was.

Now it is working perfectly.

Thank you Martin!

Was this reply helpful? Yes No