can anybody tell me how can i keep open VEGAS while building my csharp project?
whenever i build my project and if vegas is open after i test my script once then it will not let my project build.
error message shows processed by another process.
so i have to close vegas then build then again open vegas to test.
as i watch one of tutorial by @jetdv sir.. in which he suggest to add vegas210.exe in debug process. i do the same but may be i am making any mistake somewhere i cant debug it.
need help
Maybe you can use vegas200.exe for debugging?
Maybe you can use vegas200.exe for debugging?
why sir, vegas200.exe is not working well with it?
You edit, you tell it to start and it starts VEGAS with your application. Once you need to edit again, you have to shut down VEGAS. Then VEGAS will be restarted when you're ready to test again. If you don't shut down VEGAS, it can't create the new DLL file to test because VEGAS will have it locked. So just exit VEGAS each time to edit and let it restart to test.
Make sure you're adding the information exactly as I did in the tutorial. Naturally you'll need to change the path and file name for newer versions of VEGAS as version 18 was the current version when I make that script debug tutorial. You might also put the full path to the DLL file like in the Custom Command version.
For custom commands, it's slightly different and at the time of that tutorial version 19 was the current version:
This is an expected operating system behavior (Windows or any other OS). The script executable is "open" and therefore is not writable. Therefore, the recompile fails.
Of course Vegas has opened the script executable in order to run it. There is no way for Vegas to use the script without having it open.
but if we did it with .cs file then it doesn't react.
thanks all.
i will keep this in mind.
Make sure you're adding the information exactly as I did in the tutorial.
yes i did the same as you did
@iEmby, that is correct. VEGAS releases the lock on a CS file once the script is run (or it crashes). Custom Commands do not work that way. It's been a while so I don't remember if a standard script DLL will be released or not. But you need VEGAS to be started with the debug DLL in order to do the debugging (i.e. stop points and stepping through the code.)
@iEmby, that is correct. VEGAS releases the lock on a CS file once the script is run (or it crashes). Custom Commands do not work that way. It's been a while so I don't remember if a standard script DLL will be released or not. But you need VEGAS to be started with the debug DLL in order to do the debugging (i.e. stop points and stepping through the code.)
but sir i noticed something now.
i run vegas as administrator.
now i can build it. but can't paste at VEGAS Script Menu folder for replace new one.
but now i open Vegas and didn't run my dll file and try to build and replace it is going well.
so it mean if our dll file will completly shutdown / kill itself after work done. we can build and replace it.
how said about this sir?
Are you building a script, or a custom command. You definitely won't be able to replace a custom command without first shutting down VEGAS. As I said, I don't remember on a script, you might be able to. But you can't do the debugging unless you start VEGAS through Visual Studio.
i am working on custom command .dll file..
or
sir can u create a tutorial of debugging process only for Vegas.
may be it can be helpful for many like me.
That's the two videos I posted above. That's how you debug your tool in VEGAS.
Personally, at this point, most of the time I just add in some "MessageBox" commands around the area that's causing me a problem. I can show pieces of information I want to see and the last box I see before a crash narrows down to the line of code causing the crash. But it is still good to be able to do the true debugging by stepping through the code as well.