220
Views
2
Comments
DLL/Library Hell and Extension

Hi all. I have encountered the Library hell issue and I am having trouble solving it. 

I have a module (producer) that consumes an API and sends the data to another module. This producer module contains the newtonsoft nuget package. When I open this in Visual studio, it builds and works, but when I call the extension from another module, I get the following errors:

I have referred to the article:

https://success.outsystems.com/Support/Troubleshooting/Application_development/Library_hell_-_why_are_changes_in_a_producer_not_reflected_in_the_consumers

and also to similar threads and forum discussions and here is what I have attempted to fix:

1. Renamed both modules and redeployed.

2. Included the DLL file in the extension (Integration studio)

3. Re-applied changes in the consumer module.

4. Created a solution and redeployed the solution in Service Center.


The error keeps showing up as if I didn't have the library installed, but it's there!

Any help would be greatly appreciated!

2023-07-03 14-28-45
Vinicius Seixas

Update: I have marked the newtonsoft package to be downgraded to 10 instead of 13, and that seemed to solve the issue. The problem is, every time I open the extension, the package is gone and I have to re-download and re-downgrade the extension. Some progress made though. let me know if there's something else I can do to solve this. Not sure if including this in the extension again will make it stay. (it does complain if I do that).

2019-07-30 00-42-44
Kevin VanderWulp

Use the Newtonsoft.json.dll that is under C:\Program Files\OutSystems\Integration Studio, that is the one used by the platform so it wont cause collision issues

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.