Make sure you have the "EntryPoint" class.

That's why all of the scripts I've given you have:

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

A compiled DLL file should not have that issue and it can't be resolved by the end user. It almost sounds like they're trying to run a custom command as a script and that won't work.

I had wondered if he had built that based off of my tutorials. If he did - GREAT! The functionality looks very similar. The interface is cleaner but my purpose was to show the process, not make a perfect interface.

Funny enough I was finishing up the first version for testing when you started releasing the easing videos :D We've exchanged a few emails before and your videos definitely helped a ton especially when I started testing Vegas Scripting projects.

It still doesn't show up in my extensions in V20, I tried different folder locations and paste methods.
I see it in the V20 script menu, but when I click on it there, I get this:

System.ApplicationException: Failed to create instance of main class: 'EntryPoint'.
   at ScriptPortal.Vegas.ScriptHost.ScriptManager.Run(Assembly asm, String className, String methodName)
   at ScriptPortal.Vegas.ScriptHost.RunScript(Boolean fCompileOnly)

This error is only possible if you try to run it as a Script from "Tools - Scripting - Run Script..." which is not the correct way to run this extension. After placing the .dlls in the folder it should just show up under "View - Extension - Vegas Pro Flow" (you might need to restart Vegas if it was open during this time).

To confirm, you're adding the folder into "My Documents" - wherever that happens to be.

If you're on Windows 11, there's a differences between [user name]\Documents (which won't be seen by VEGAS) and [user name]\OneDrive\Documents (which will be seen by VEGAS)

That's why I always say to put custom commands in:

[My Documents]\Vegas Application Extensions

and regular scripts in:

[My Documents]\Vegas Script Menu

Very interesting, I had no idea this could even be a possible problem. I'll add this to the description, thank you for sharing it!

Welcome @RatinFX! 😁🙌

@RatinFX, I figured it sounded like running as a script instead of a custom command.

Yes, Win11 certainly added a new twist. I figure just saying "[My Documents]\Vegas Application Extensions" will work everywhere as Win11 points to the One Drive folder for "My Documents". When I first got my Win 11 machine, I tried both places just to see what would happen. Even though I've turned off "One Drive", it's still used for "My Documents".

Glad to see this new extension available.

It still doesn't show up in my extensions in V20, I tried different folder locations and paste methods.
I see it in the V20 script menu, but when I click on it there, I get this:

System.ApplicationException: Failed to create instance of main class: 'EntryPoint'.
   at ScriptPortal.Vegas.ScriptHost.ScriptManager.Run(Assembly asm, String className, String methodName)
   at ScriptPortal.Vegas.ScriptHost.RunScript(Boolean fCompileOnly)

This error is only possible if you try to run it as a Script from "Tools - Scripting - Run Script..." which is not the correct way to run this extension. After placing the .dlls in the folder it should just show up under "View - Extension - Vegas Pro Flow" (you might need to restart Vegas if it was open during this time).

Thank you, I was aware of that. I tried every possible location for the files, as well as having it as a timeline tool icon. Even when pressing the icon I get an error message.

System.ApplicationException: Failed to create instance of main class: 'EntryPoint'.
   at ScriptPortal.Vegas.ScriptHost.ScriptManager.Run(Assembly asm, String className, String methodName)
   at ScriptPortal.Vegas.ScriptHost.RunScript(Boolean fCompileOnly)

@jetdv Any idea why it wouldn't show up for some people in either folder without any errors or exceptions on any Windows version?

@Mindmatter, it has to be started as a custom command/extension. It's not a "script".

@RatinFX, really the only case I can think of that would cause it to not work would be trying to load the "13" version in 14 or newer or the "14" version in 13 or older.

I've discovered you can have two version, both 13/older and 14/newer, installed at the same time and VEGAS will pick the one it can use. That's what I've done with Excalibur, both "Sony" and "ScriptPortal" can be installed at the same time and they both share the common folders and config files.

Thanks jetdv, I know.
I found it and feel pretty silly...all this time I've looked under "tools---> extensions" instead of "view...extensions"

sorry for the mess!

Release: 1.0.2 Mar 29, 2023

Added Settings option to toggle "Check for Updates on Start"
Refactored the About tab

Release: 1.0.3 Mar 29, 2023

Fixed multiple issues with Adding new Custom Curves
Added a warning for Track Motion animating, make sure you close the window before applying curves!
Slightly increased the size of the curve name boxes

Release: 1.4.1 May 14, 2023

Changed versioning
Moved from Views to Tools - Extensions
Renamed Track Pan/Crop to Track Motion
Added support for Parent Track Motion, Parent Track Glow and Parent Track Shadow
Added support for Track Envelopes: Mute, Composite level, Fade to color
Added support for Event Envelopes: (Fade in & Fade out) Transition Progress, Velocity
Check for Updates on Start is enabled by default on the first start
Display all selectable Track, Event, and Envelope options by default

Release: 1.4.2 May 14, 2023

Removed Mute from supported Track Envelopes
Fixed various Fade in/out Transition Progress Envelope issues

Thanks for the update.

Just a note, that the default installation goes to C:\Users\[username]\AppData\Roaming\VEGAS Pro\Application Extensions , and I can't find in the Tools - Extension.

Like above's previous post (and in my Win10 O version), it should be copied to C:\Users\[username]\Documents\Vegas Application Extensions

Quoting from the VEGAS Scripting FAQ, any of the following folders should work for an extension:

• C:\Users\<username>\Documents\Vegas Application Extensions\
• C:\Users\<username>\AppData\Local\VEGAS Pro\17.0\Application Extensions\
• C:\Users\<username>\AppData\Roaming\VEGAS Pro\17.0\Application Extensions\
• C:\ProgramData\Vegas Pro\17.0\Application Extensions\
• C:\Users\<username>\AppData\Local\Vegas Pro\Application Extensions\
• C:\Users\<username>\AppData\Roaming\Vegas Pro\Application Extensions\
• C:\ProgramData\Vegas Pro\Application Extensions\

I tried to find the most reliable path but it seems like no one choice worked for everyone so far.

At the same time showing all these options to the end user is just asking for trouble as I would end up becoming Customer Support.

If it is Sony Vegas, the .dll should be placed in the directory here (don't create any subfolder):

• C:\Users\<username>\Documents\Vegas Application Extensions\
• C:\Users\<username>\AppData\Local\Sony\Vegas Pro\13.0\Application Extensions\
• C:\Users\<username>\AppData\Roaming\Sony\Vegas Pro\13.0\Application Extensions\
• C:\ProgramData\Sony\Vegas Pro\13.0\Application Extensions\
• C:\Users\<username>\AppData\Local\Sony\Vegas Pro\Application Extensions\
• C:\Users\<username>\AppData\Roaming\Sony\Vegas Pro\Application Extensions\
• C:\ProgramData\Sony\Vegas Pro\Application Extensions\

Therefore, the best path to place the .dll is: 
C:\ProgramData\VEGAS Pro\Application Extensions\ 
or 
C:\ProgramData\Sony\Vegas Pro\Application Extensions\  
It can make suer that all versions of Vegas Pro can load them, and does not contain any system user name or Vegas version name.

Therefore, the best path to place the .dll is: 

C:\ProgramData\VEGAS Pro\Application Extensions\ 
or 
C:\ProgramData\Sony\Vegas Pro\Application Extensions\  

I disagree. I still say the best place is:

[My Documents]\Vegas Application Extensions (for extenstions)

[My Documents]\Vegas Script Menu (for regular scripts)

Much easier to find and will work with ALL versions of VEGAS installed.

Therefore, the best path to place the .dll is: 

C:\ProgramData\VEGAS Pro\Application Extensions\ 
or 
C:\ProgramData\Sony\Vegas Pro\Application Extensions\  

I disagree. I still say the best place is:

[My Documents]\Vegas Application Extensions (for extenstions)

[My Documents]\Vegas Script Menu (for regular scripts)

Much easier to find and will work with ALL versions of VEGAS installed.

I would love to keep things in [Documents] but from the feedback I received it looks like not one single path worked consistently for all users.

All of my installers (Excalibur, Montage Magic, Auto Save, Project Inspector, etc...) install into [My Documents]\Vegas Application Extensions and I've never had anyone tell me it doesn't work from there.

In fact, every one of these paths works for me (You need to make sure the dlls are in these paths, not in their subfolders.). I like C:\ProgramData\VEGAS Pro\Application Extensions\ because it is an absolute path. I just need Copy&Paste it to any computer, to open it. And it will never stop working even though different computers have different user names.

All of my installers (Excalibur, Montage Magic, Auto Save, Project Inspector, etc...) install into [My Documents]\Vegas Application Extensions and I've never had anyone tell me it doesn't work from there.

I have multiple Vegas Pro 18 and 20 users telling me it's not working meanwhile every path works on my PC for Vegas 14 and 18, I'm not sure what's going on at this point.

Sadly I don't have Vegas 20 so I can't even test some other problems they shared 😓

@RatinFX The key is that it MUST go under the actual "My Documents" folder which, on my Win11 system, is now under "OneDrive". When installing, my installer users they actual "My Documents" variable to get the correct install location.

You CANNOT just install under "Users\[user name]\Documents" anymore as that may or may not be the correct location. On my Win10 system, that is where "MY Documents" is located. On my Win11 system, it is not.

That's why I'm trying to be very clear that it must be "My Documents" and not just a "Documents" folder under "User name".

@jetdv I understand, it must be the Environment.SpecialFolder.MyDocuments enum in C# and %userprofile%/Documents in Windows Explorer, right?