Skip to main content
Solved

Editing Existing .dll Extension Libraries

  • 3 September 2024
  • 3 replies
  • 62 views

Hi Everyone 

I have a customization package that have been developed on another consultant's locally hosted instance. They have used an extension library (.dll compiled project) where graphs have been extended to visual studios.

I want to edit this customization package's graphs that have been extended via the .dll file. I tried importing the customization package to my local host and extending the extension library to edit the VS extended graphs but when I open the project, the graphs are not there and only an Example.cs class is loaded.

What is the correct route to follow when editing graphs that has been extended to a Extension Library on someone else's local instance which you want to edit on your own local instance?

Best answer by Dmitrii Naumov

@dewaldblaauw12 usually in this case you remap DLL dependencies in VS manually. If you’d like the DLL to be put directly in the bin folder of the site during the build, you can also set up Build path or post build even in Visual studio.

View original

Dmitrii Naumov
Acumatica Moderator
Forum|alt.badge.img+6

@dewaldblaauw12 You’ll need to get the source code of the solution from that other developer and work with the source code itself. 

 

If it’s not possible to get the source code, you can probably use one of the available decompilers (e.g. ILSpy, JetBrains decompiler, etc.) to extract the code from the DLL (may require some manual edits after that). If you need to go this way, please make sure you have the legal right to do that (e.g. the source code is not an intellectual property of some other entity).


Dmitrii Naumov wrote:

@dewaldblaauw12 You’ll need to get the source code of the solution from that other developer and work with the source code itself. 

 

If it’s not possible to get the source code, you can probably use one of the available decompilers (e.g. ILSpy, JetBrains decompiler, etc.) to extract the code from the DLL (may require some manual edits after that). If you need to go this way, please make sure you have the legal right to do that (e.g. the source code is not an intellectual property of some other entity).

Hi Dmitrii. Thank you very much for this. 

Currently I have the source code and I also used a decompiler to extract the code. 

The problem is that I don’t know where to extract this code to in order to be able to edit it via VS and to build the project and reference it under the file section of the Customization Project Editor. 

 

For Example I have the following scenario where I have the project and I extracted the zip folder containing the project like done here 

When I open this project in VS I get so many errors (as indicated below): 

It seems like the assemblies doesn’t get loaded. As one would normally do is build a solution after editing an extension and these changes will be loaded to the .dll on the File section of the Customization Project Editor, but the source code is currently standalone and not binded with a extension library. I am not quite sure how this works and integrates with the Customization Project Editor. 

 

Any help on this would be greatly appreciated. 


Dmitrii Naumov
Acumatica Moderator
Forum|alt.badge.img+6

@dewaldblaauw12 usually in this case you remap DLL dependencies in VS manually. If you’d like the DLL to be put directly in the bin folder of the site during the build, you can also set up Build path or post build even in Visual studio.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings