Debugging in version 21 build 315? Or probably previous builds too.

ccscotty wrote on 5/24/2024, 12:41 AM

Does anyone have class library DLL script debugging working with Vegas Pro version 21 build 315 in Visual Studio 2022 community edition? (Version 17.10.0 which is the latest stable build)

The output I get is this: "The program '[17316] vegas210.exe' has exited with code 0 (0x0)." Vegas never shows the startup splash screen or anything else.

With the ScriptingPortal.Vegas DLL switched in references between that and version 19, this version of Visual Studio appears to be working fine with Vegas Pro 19, but none of my latest projects are in version 19 anymore.

I can likely develop and debug with version 19, but that adds extra time and hassle to the process.

I use features of C# version 7+, so going back to an older version of Visual Studio is difficult. I did find the Visual Studio 2015 community ISO in the past, but haven't been able to get the NuGet packages "Microsoft.Net.Compilers.Toolset" and "System.ValueTuple" working. Maybe a middle of the road version of Visual Studio could work, but finding the community editions of anything besides 2022 is difficult or impossible now. Even so has anyone gotten VS 2017 or VS 2019 working with Vegas Pro 21?

Comments

jetdv wrote on 5/24/2024, 8:41 AM

I still create my scripts in VS2015 (for multiple reasons - proper debugging is only one of them). I've played with 17 and 19. Just finding the correct starting preset is horribly more difficult in those two versions. Debugging in those two versions caused the tab header lines in VEGAS to be solid white in my testing. I've never tried 22.

ccscotty wrote on 5/24/2024, 12:13 PM

I still create my scripts in VS2015 (for multiple reasons - proper debugging is only one of them). I've played with 17 and 19. Just finding the correct starting preset is horribly more difficult in those two versions. Debugging in those two versions caused the tab header lines in VEGAS to be solid white in my testing. I've never tried 22.

Thanks for the information! I managed to get Visual Studio 2017 and re-created the project with it. The same thing happened with Vegas 21 build 315 where it doesn't startup on debug, so I'm thinking the problem is Vegas.

Which version of Vegas are you using?

jetdv wrote on 5/24/2024, 4:00 PM

@ccscotty with scripting, versions 4 through 21. I actually haven't tried to start in debugging mode in 21, though.

ccscotty wrote on 7/15/2024, 2:55 PM

After having issues with 315, I tried build 208 of version 21. It has the same problem where Vegas doesn't start when attempting to debug. It looks like it wasn't anything specific to recent builds. Same situation with Visual Studio 2017 and 2022.

The program '[12596] vegas210.exe' has exited with code 0 (0x0).

 

 

jetdv wrote on 7/16/2024, 7:13 AM

@ccscotty, you may find it started with previous versions...

bitman wrote on 7/16/2024, 10:38 AM

I never bothered with a proper IDE for my vegas scripts, I am almost ashamed to admit I just use notepad++!

Works all the time. Debugging values is done by adding a temporary message box.

Using a proper IDE is a tremendous help for Vegas scripts, but even with notepad++ I am crafty enough in finding bugs quickly, probably because I have 30+ years of debugging code as a software tester in both assembler and Java...

APPS: VIDEO: VP 365 suite (VP 22 build 194) VP 21 build 315, VP 365 20, VP 19 post (latest build -651), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 17 HDpro XXL, Boris Continuum 2025, Davinci Resolve Studio 18, SOUND: RX 10 advanced Audio Editor, Sound Forge Pro 18, Spectral Layers Pro 10, Audacity, FOTO: Zoner studio X, DXO photolab (8), Luminar, Topaz...

  • OS: Windows 11 Pro 64, version 24H2 (since October 2024)
  • CPU: i9-13900K (upgraded my former CPU i9-12900K),
  • Air Cooler: Noctua NH-D15 G2 HBC (September 2024 upgrade from Noctua NH-D15s)
  • RAM: DDR5 Corsair 64GB (5600-40 Vengeance)
  • Graphics card: ASUS GeForce RTX 3090 TUF OC GAMING (24GB) 
  • Monitor: LG 38 inch ultra-wide (21x9) - Resolution: 3840x1600
  • C-drive: Corsair MP600 PRO XT NVMe SSD 4TB (PCIe Gen. 4)
  • Video drives: Samsung NVMe SSD 2TB (980 pro and 970 EVO plus) each 2TB
  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB
  • MOBO: Gigabyte Z690 AORUS MASTER
  • PSU: Corsair HX1500i, Case: Fractal Design Define 7 (PCGH edition)
  • Misc.: Logitech G915, Evoluent Vertical Mouse, shuttlePROv2

 

 

ccscotty wrote on 7/16/2024, 10:47 AM

I never bothered with a proper IDE for my vegas scripts, I am almost ashamed to admit I just use notepad++!

Works all the time. Debugging values is done by adding a temporary message box.

Using a proper IDE is a tremendous help for Vegas scripts, but even with notepad++ I am crafty enough in finding bugs quickly, probably because I have 30+ years of debugging code as a software tester in both assembler and Java...

Yeah, I've been programming since the late 1990s. I'd rather have tools to help me not waste time but it's (Edit: partly... found a few workarounds) not going to be the case for Vegas moving forward. I got better information from them this time explaining why they made the change.

ccscotty wrote on 7/16/2024, 11:03 AM

Wwaag provided a piece of code that should be helpful to at least iterate on the code faster.

vegas.UnloadScriptDomainOnScriptExit = true;

I haven't tried it yet, but presumably Vegas can continue running and I'd be able to recompile the script after a change.