I've got a very basic .NET extension project (obviously the full project will be much bigger) but I'm having trouble getting it to work.  I'm using SalesLogix v7.5.2, and have created a simple .NET 3.5 class library:

using Sage.SalesLogix.NetExtensions;
using System.Windows.Forms;
 

namespace SLxTest
{
    public class Class1 : BaseRunnable
    {
        public override object Run(object[] args)
        {
            MessageBox.Show("Hello World");
            return "Hello";
        }
    }
}

And the calling code in SalesLogix is on the OnCreate event handler:

Sub AXFormCreate(Sender)
    Dim ext
    Dim id
 

    ext = Application.Managed.Create("SLxTest", "SLxTest.Class1")
    Set id = Application.Managed.Run(ext)
End Sub

On the 'Set id...' line I get the 'Object required: 'Application.Manager.Run(...)'' error message from VBScript.  I've looked around and checked the 5 .dll files (listed in 'RegisterSLXNetExtentions.bat' file, which also appears to execute correctly).  Strangely enough, when stepping through at breakpoint in VBScript, the 'ext' variable is correctly populated with some GUID looking value.  The .NET extension is also released to everyone, so I don't think it's a release problem.

Any help would be greatly appreciated...

Dan Brentley

Since you're not returning an object back from the extension, no need to use "Set". Remove that and all else looks fine to me.

Hi Ryan,

Thanks for the reply; I tried that and then although I didn't get an error message, the message box (from the .NET code) didn't appear and the id variable wasn't populated (still 'Empty').  I've realised though that all the examples I've seen require at least one additional argument (on top of the 'ext' variable) to be passed to the Application.Managed.Run() method.  So the code now executes correctly once the VBScript is changed to:

Sub AXFormCreate(Sender)
    Dim ext
    Dim id
 

    ext = Application.Managed.Create("SLxTest", "SLxTest.Class1")
    id = Application.Managed.Run(ext, "")
End Sub

Even if I'd noticed that before, I'd probably have still then got confused by the resultant error message from not removing the 'Set' command, so thanks for the heads up!

Dan Brentley

Ah, yes. Didn't notice that in your original code. You do need the second parameter. Blank string or Empty works fine.