I am debugging in Server 2019 VS2019

Sage200scripts is a class library compiled into the working folder of Sage200Desktop.exe

the below script should work in w10 (looks like TAB characters are not liked in the script)

Imports System
Imports System.Windows.Forms
imports Sage200Scripts

Module addInModule

Public Sub Main()

Dim script As New Sage200Scripts.FormAmendments()
script.Run(form)

End Sub
End Module

jON

I am debugging in Server 2019 VS2019

Sage200scripts is a class library compiled into the working folder of Sage200Desktop.exe

the below script should work in w10 (looks like TAB characters are not liked in the script)

Imports System
Imports System.Windows.Forms
imports Sage200Scripts

Module addInModule

Public Sub Main()

Dim script As New Sage200Scripts.FormAmendments()
script.Run(form)

End Sub
End Module

jON

compile the project

remove your compiled dll from the sage200desktop folder that you mention

run sage 200

 put you Sage200Scripts dll in the 

c:\users\jon\appdata\local\sage\sage200\assemblycache folder

make sure you .vbs script is in the scriptcache folder

and then trigger whatever you are doing to run the script in sage 200

see what happens.

i have had much weirdness with the .VBS files over the years,  and several times for no reason, i have just had to create a new one from an empty not pad.

This is entirely caused by the fact that the third Imports statement in the file above should be capitalized - Imports.

Dang goods eyes you have Chris!!

Aye, even at my age.

The ScriptManager class which parses and compiles the .vbs files at runtime does, for the most part, recognise the fact that VB is case insensitive. Where it doesn't do that is when it's reading the top of the file for Imports or Options statements - it expects them to be capitalized.  Unfortunately, if it finds a lowercase 'imports' (or 'options') then it doesn't ignore them - it incorrectly assumes it's found its way into the main body of the code and ends up compiling a load of garbage - hence the multiple errors.

I agree ... I had already fixed that by the time I tested on my 2019 server and its working fine now. Many thanks for the feedback guys.