I didn't see any "Using" statements in your script. You do NOT need to copy those other files to the script menu folder.

All scripts and custom commands are working just fine in all versions of VEGAS here without copying any of those files.

I already had Using statements at the begining of my plugins:

using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using System.Windows.Forms;
using ScriptPortal.Vegas;

I do also had them for a very long time, but after latest Vegas Pro build some of the plugins stopped me working.

I noticed that copied all the files I mentioned in previous solved the issue.

I didn`t have any problems with my plugins before latest Vegas Pro update.

That's why I was very shocked.

@jetdv

Jetdv, If I had not had "using ScriptingPortal.Vegas" statement before, my all Vegas code would not even compiled and my dll would not even been created. That's why it was weird why it throws the error I mentioned in first post.

I've had every build of VEGAS Pro 20 and this has not been an issue.

@jetdv

I also had every build of Vegas Pro 20, and this has not been an issue so far, till today.

I didn`t think up the error issue:

System.ApplicationException: Suitable entry point method, 'FromVegas', not found.
   at ScriptPortal.Vegas.ScriptHost.ScriptManager.Run(Assembly asm, String className, String methodName)
   at ScriptPortal.Vegas.ScriptHost.RunScript(Boolean fCompileOnly)

Maybe it was some Windows 10 issue, I don`t know, but copying files helped it.

I'd try removing the files you copied, uninstall VEGAS, and then reinstall VEGAS. There's definitely something odd with your VEGAS installation at this point.

I'd try removing the files you copied, uninstall VEGAS, and then reinstall VEGAS. There's definitely something odd with your VEGAS installation at this point.

I'm having similar issue -- trying to run a script I wrote that was doing well pre V20 and now I'm getting that error.. don't use these often enough to know root cause yet -- just trying to get it running..

I know I've been down similar road before but this is a bit different... can't get this script to run either in debug mode from VS, or starting within Vegas.

When in VS if I choose "Debug->Start Debugging", I get this:

If I build the solution and try running it from Vegas (Tools.Vegas.Run Script), pointing to the .dll that was generated (in the source.repos.myprojectnameproject.myprojectnameproject.bin.Release) I get the "Suitable entry point method, 'FromVegas', not found. (message missing):

And I definitely have a 'FromVegas' method defined... this was working last time I'd tried it... (several months ago or more)

There must be an easy way to get over this hump... I'd happily run it in Debug mode (preferred) or direct started within Vegas.. just need to get it running. Debug Mode is a bonus since I've just added new functionality I'd love to debug if it doesn't work right the first time (ha!).

PS @jetdv Thank you for your short little videos.. they've helped get me in the right direction more than once!

UPDATE: From inside VS I got it to launch in debug mode but it was trying to load Vegas 18... when I changed it to Vegas 20's EXE (properties, debug, Start external program), the output window returns pretty quickly saying "The program '[36348] vegas200.exe' has exited with code 0 (0x0), but it never actually appears to launch. Changed it back to the Vegas 18 executable, but when I run the script I'm getting the same "FromVegas" not found error.

System.ApplicationException: Suitable entry point method, 'FromVegas', not found.
   at ScriptPortal.Vegas.ScriptHost.ScriptManager.Run(Assembly asm, String className, String methodName)
   at ScriptPortal.Vegas.ScriptHost.RunScript(Boolean fCompileOnly)
 

Welp... I put back the Vegas 18 scriptportal.vegas.dll, and set the project to launch Vegas 18 and now I'm at least able to get my code debugging... just nada when trying to use Vegas 20 and its version of the dll :(

@RedRob-CandlelightProdctns First of all, the scriptportal dll file does not need to be copied into the same folder as your compiled DLL file. Also, it should not be added to your project as shown in the third image. It SHOULD chosen be in "references" but does not need to be directly added to the project.

I can say I have not seen this issue with either text scripts or compiled scripts. I would need to see the full project in order to do any testing.

Will the script work if you run it as plain text instead of compiled?

Start with something simple and verify things are working. Save this as "test.cs" and see if it runs properly:

using System;
using System.Collections.Generic;
using System.Collections;
using System.IO;
using System.Text;
using System.Windows.Forms;
using System.Globalization;
using System.Drawing;
using System.Runtime;
using System.Xml;
using ScriptPortal.Vegas;

namespace Test_Script
{
    public class Class1
    {
        public Vegas myVegas;

        public void Main(Vegas vegas)
        {
            myVegas = vegas;

            MessageBox.Show("This Script Started Fine");
        }

    }
}

public class EntryPoint
{
    public void FromVegas(Vegas vegas)
    {
        Test_Script.Class1 test = new Test_Script.Class1();
        test.Main(vegas);
    }
}

@marcinzm By the way, in the first post in this thread, I just noticed a "}" is missing in the top section. Please note that "EntryPoint" is OUTSIDE the "Namespace" section:
 

namespace VegasJumpingCutScript
{
    public partial class Form1 : Form
    {
        public Vegas myVegas;

        public Form1(Vegas vegas)
        {
            myVegas = vegas;
            InitializeComponent();

//            my code here
        }
    } <--- This one is missing!

}

public class EntryPoint
{
    private static VegasJumpingCutScript.Form1 form;

    public void FromVegas(Vegas vegas)
    {
        form = new VegasJumpingCutScript.Form1(vegas);
        form.ShowDialog();
    }
}

I just came across this problem of message missing, System.ApplicationException: Suitable entry point method, 'FromVegas', not found myself. Eventually I found the cause and solution!

From the other messages above: EntryPoint can be inside the namespace, no problem!

It is caused by referencing an older version of ScriptPortal.Vegas in your project and running it in a newer version of Vegas. I had my reference to ScriptPortal.Vegas from the Vegas 21 version, which I loaded in Vegas 22 when I got the same error.

Solution:

Change the reference in your project to the latest version of Vegas. So in my case I removed the reference to the Vegas 21 version of ScriptPortal.Vegas and added the reference to the 22 version of ScriptPortal.Vegas.

For me that solved the problem!

@VegaMega, I often reference the VEGAS Pro 14 ScriptPortal and run the scripts in versions 14 through 22. So could you please better explain what you did?

If I need to use some "newer" features, I certainly reference a newer ScriptPortal file that can do those features but, otherwise, I've seen no need to always reference the newer version.

The issue above was the missing "}".

I found that referencing scriptportal dll in Vegas 21 while running Vegas 22 caused this same error. That's all. Just make sure you reference scriptportal in the version you are actually using.

In general is it always a good idea to use the latest versions. It is not so much about functionality that you may or may not need. It is more a good practice and from a security point of view essential (although a case can be made for such a local program). Secondly, in general, fixing small incremental issues by continues updating is way easier than skipping many versions and finding your program to be completely incompatible with the new version.

I don't like it either (keeping it fixed on 1 version is way easier), but it is how things work in the world! After all, nobody is using Windows 3.11 anymore, right?

So: Always use the latest version! Just for good practice!

@VegaMega, except that won't work when you're dealing with writing scripts for multiple people that use multiple versions. If I'm using a newer features that was added to ScriptPortal later, then I have to specify exactly which version(s) this script works with. Otherwise, I try to keep things as generic as possible to that it still works with people using version 14 or newer. But they still work fine in 22 with no issues.

I've just not seen any issues with it not finding "FromVegas" without it being a coding error no matter which ScriptPortal DLL is used.

@jetdv well, you are right about that! It should remain at least upwards compatible and a script should specify a minimum version and run also on the newer version.

So I checked again!

Basic script:

using System;
using ScriptPortal.Vegas;

namespace VegasProScriptingExample
{
    public class EntryPoint
    {
        public void FromVegas(Vegas vegas)
        {
            vegas.UnloadScriptDomainOnScriptExit = true;

            // Example: Display a message box
            System.Windows.Forms.MessageBox.Show("Hello from Vegas Pro Script!!!!!");

            // Your scripting logic here
        }
    }
}

Using Visual Studio 2022 and building against .Net Framework 4.8.

• I made a build with a reference to the ScriptPortal.dll from Vegas 21.0
• I made a build with a reference to the ScriptPortal.dll from Vegas 22.0

I tried these both in Vegas 21.0 as well as in Vegas 22.0.

This is the result:

• Vegas 22.0 does not work with the ScriptPortal.dll from Vegas 21.0
• Vegas 22.0 does work correctly with the ScriptPortal.dll from Vegas 22.0
• Vegas 21.0 does work correctly with the ScriptPortal.dll from Vegas 21.0
• Vegas 21.0 does not work with the ScriptPortal.dll from Vegas 22.0

With "Does not work", it resulted in:

An error occurred during execution of the script .
Error 0x80131600 (message missing)

details:
System.ApplicationException: Suitable entry point method, 'FromVegas', not found.
   at ScriptPortal.Vegas.ScriptHost.ScriptManager.Run(Assembly asm, String className, String methodName)
   at ScriptPortal.Vegas.ScriptHost.RunScript(Boolean fCompileOnly)
 

So, there is definitely a problem.

Would be nice to hear if others have the same results.

Also (different subject): If anyone has debugging from VS2022 working, please let me know!!!

@VegaMega, here's your problem. When you compile, it's also copying "ScriptPortal.dll" into the compiled folder. Then when you start the script, it's referencing the wrong DLL file. Go to the compiled folder and delete the extra DLL files and try it again.

With the copied files in the folder, I can duplicate your results. Without the copied files in the folder (i.e. only the ONE rendered DLL file), it works fine.

Click on ScriptPortal.dll and change "Copy Local" to False.