Feedback
Did this article resolve your question/issue?

   

Article

Is it possible to remove all assemblies from assemblies.xml that are not directly referenced by ABL code?

Information

 
TitleIs it possible to remove all assemblies from assemblies.xml that are not directly referenced by ABL code?
URL Nameis-it-possible-to-remove-all-assemblies-from-assemblies-xml-that-are-not-directly-referenced-by-abl-code
Article Number000138595
EnvironmentProduct: OpenEdge
Version: 11.x
OS: All supported Windows platforms
Question/Problem Description
Is it possible to remove all assemblies from assemblies.xml that are not directly referenced by ABL code?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
You have to make sure, what is minimum assemblies required to compile the code and run compiled code without any runtime errors. It is possible to find out what dependencies are essentials for running the code, by using 3-rd party products like Process Explorer or .NET Dependency Walker. 

When using Process Explorer follow the steps: 
- download Process Explorer (use the link from the note section)
- press Ctrl+L to enable Lower Pane 
- select prowin.exe to see the list of handles and dlls required for process
- save the output to .txt file by pressing Crtl+A

Lets take an UltraWinGrid as an example. If you add this control to the form, following dependencies are added to the assemblies.xml:
Infragistics4.Shared.v16.2
Infragistics4.Win.Misc.v16.2
Infragistics4.Win.UltraWinGrid.v16.2
Infragistics4.Win.v16.2
Microsoft.VisualBasic
System
System.Core
System.Data
System.Drawing
System.Runtime.Serialization.Formatters.Soap
System.Windows.Forms
System.Xml
UIAutomationProvider
UIAutomationTypes

If you compile the form and then run the compiled code from proenv, process explorer shows that following assemblies are required for process to run:
File C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Infragistics4.Win.v16.2\v4.0_16.2.20162.2182__7dd5c3163f2cd0cb\Infragistics4.Win.v16.2.dll
File C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Infragistics4.Shared.v16.2\v4.0_16.2.20162.2182__7dd5c3163f2cd0cb\Infragistics4.Shared.v16.2.dll
File C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Infragistics4.Win.UltraWinGrid.v16.2\v4.0_16.2.20162.2182__7dd5c3163f2cd0cb\Infragistics4.Win.UltraWinGrid.v16.2.dll
File C:\Windows\Microsoft.NET\assembly\GAC_MSIL\UIAutomationProvider\v4.0_4.0.0.0__31bf3856ad364e35\UIAutomationProvider.dll
File C:\Windows\Microsoft.NET\assembly\GAC_MSIL\UIAutomationTypes\v4.0_4.0.0.0__31bf3856ad364e35\UIAutomationTypes.dll

Based on above assemblies.xml has to contain at least the following assemblies for the code to compile and run:
Infragistics4.Shared.v16.2
Infragistics4.Win.UltraWinGrid.v16.2
Infragistics4.Win.v16.2
UIAutomationProvider
UIAutomationTypes

The rest assemblies are in this particular case redundant and can be removed from assemblies.xml without causing compile problems or runtime errors.
Workaround
Notes
References to other documentation:

Progress articles(s):
 How does the Progress client handle .NET assembly loading

Microsoft article(s):
Process Explorer, https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer
Last Modified Date11/20/2020 7:03 AM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.