Can I debug extension with dependencies like dll or a nuget package?

zzzzzz9125 wrote on 9/7/2025, 8:51 AM

The following question was asked by my friend who is learning scripting in VEGAS Pro. I can't answer it. Sincerely ask everyone on the forum for help.

Hi, I'm encountering a problem with custom command DLLs in Vegas Pro. When I create a simple extension DLL with no external dependencies, Vegas can load it without issues. However, if my project references another class library or a NuGet package, it simply does not appear in the extensions menu.

It seems like Vegas cannot resolve dependent assemblies automatically. Has anyone experienced this? Are there recommended ways to handle dependencies for custom command projects so that Vegas can load them correctly?

Comments

bvideo wrote on 9/7/2025, 11:28 AM

Maybe part of the question is "how to tell Vegas where to find" the package referenced (on the user's system). Another approach is "how to bind an external package as part of the dll."

Howard-Vigorita wrote on 9/7/2025, 1:18 PM

When writing a c# script with a text editor, "using" statements work for some assemblies shipped with Vegas, like "using System", but not for others like "using System.Linq". There might be a way to drop the missing assembly dll into a folder somewhere but I don't know that trick. I've never tried just dropping the missing dll into the Vegas scripts folder... that might work.

Using Visual Studio and then compiling the script to a dll is the way I've been doing it. However even Visual Studio only installs by default with a limited number. But it has an extensive list of assemblies online that can be selected, downloaded, and made available to it locally.

jetdv wrote on 9/7/2025, 1:56 PM

Take a look at this tutorial which loads a DLL not referenced by VEGAS from a script. The similar may be the same with an Extension.

Or you could try copying the needed DLL(s) in the same folder as the Extension.

zzzzzz9125 wrote on 9/7/2025, 2:07 PM

@bvideo @Howard-Vigorita @jetdv Regarding the problem he encountered, I would like to explain it in more detail: He wants to use the Debug feature in Visual Studio and correctly use external libraries on this basis.

For the debug feature in Visual Studio, see: https://www.vegascreativesoftware.info/us/forum/debugging-with-visual-studio-2022--147372/#ca926339

Also according to this post, it seems that starting from VP20, VEGAS Pro blocked the debug feature. My friend is using VP18 and he wants to use debug. He can debug projects without additional dependencies normally in VP18, but once additional dependencies are included, VP refuses to load it.

Since I've been using the latest build of VEGAS Pro all along, I'm unable to use the debug feature. I can only compile Release and place it in the extension folder to load it. Of course, we all know that in this case, by placing the external dependencies used in the same folder as the extension DLL we compiled, they can be loaded. However, when my friend tried to debug, he didn't know how to make the external dependencies work properly as well. It seems that no tutorial has mentioned this point, so I'm very confused too.

jetdv wrote on 9/7/2025, 2:13 PM

Yes, debugging has not worked in the recent versions of VEGAS. I haven't tried starting in "debug" mode since then. Typically, I'll now just use "MessageBox" messages to track the progress through specific routines and any specific variable values I want to see.

I would still think that even in debug mode as long as the other DLLs are in the same folder it should see them but it may not. When compiling, there's certainly an option to copy the dependent DLLs too.

Howard-Vigorita wrote on 9/7/2025, 3:42 PM

@zzzzzz9125 I recall the Voukoder developer mentioning the same thing and that he had to ship his dlls to the Vegas developers to do the debugging for him. He did not mention if there was any cost for such support or what the conditions might be. Your friend may need to make contact with Vegas developers for debugging support.