How to add New Controls so that ABL picks them up

Posted by solvieg on 20-Feb-2011 07:57

Hi,

I have created a new .Net Numeric TextBox Control that inherits the original Textbox control in C#. However, I'm having problems getting the ABL Eclipse to recognize the control:

The error is

A problem has occurred while loading the assembly 'path\NumberBox.dll'

The assembly or one of its dependencies could not be loaded.

A second question is:

In c# I have the following code

namespace NumericFormat
{
    public enum NumericMask { Decimal, Integer, Digit };
   
    public class NumericFormatTextBox : System.Windows.Forms.TextBox
    {
        #region [ Variables ]
        private NumericMask m_mask = NumericMask.Integer;
        private System.Windows.Forms.ErrorProvider errorProvider1;
        private System.ComponentModel.Container components = null;

        public NumericMask Masked
        {
            get { return m_mask;}
            set { m_mask = value; }
        }

How do I define the public enum NumericMask in ABL code

I'm a Progress developer, also developed in C# but new to the Progress GUI for .Net, so any assistance would be greatly appreciated.

TIA

All Replies

Posted by Admin on 20-Feb-2011 08:16

A problem has occurred while loading the assembly 'path\NumberBox.dll'

The assembly or one of its dependencies could not be loaded.

On OpenEdge project properties in OpenEdge Architect, did you use an -assemblies Parameter?

If not, your custom .dll/Assembly needs to be in the project root directory (assuming you are not using a shared AVM). When you are using an -assemblies parameter the .dll needs to be in the directory referenced by that parameter.

In general your .dll needs to be in the same folder as the file assemblies.xml that references it. The sub folder (path) in your assemblies name suggests that you are violating this rule.

Also make sure the assembly is compiled with .NET 2.0, 3.0 or 3.5

.NET 4.0 is not yet supported.

Posted by solvieg on 20-Feb-2011 08:46

Hi Mike,

The issue was that the control was compiled in .Net 4.0. As soon as I changedc the compilation to 3.5, the Eclipse ABL picked it up.

Thanks.

Posted by Admin on 20-Feb-2011 09:46

The issue was that the control was compiled in .Net 4.0. As soon as I changedc the compilation to 3.5, the Eclipse ABL picked it up.

 

Support for .NET 4.0 seems to be on the roadmap for OE11. (might change any time without notice).

This thread is closed