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

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!!

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.