Comments

JohnnyRoy wrote on 9/24/2009, 7:55 AM
Are you getting an error message when it fails? If so, what is it? Vista has much stronger security so things that worked in XP may not work on Vista. What extensions is it? Did you write it? Do you have the necessary .Net Framework installed for it if it requires anything older that 3.0?

~jr
ibrahimdursun wrote on 9/24/2009, 10:34 PM
Hi Johnny,

>Are you getting an error message when it fails?
It does not show any error. I don't know where to look for logs.

>What extensions is it? Did you write it?
Our company is writing an extension to integrate one of our product with Vegas.

.Net Framework 3.5, 3.0, 2.0 and 1.1 are already installed.

So I am asking:
1. Where can I find the log? If I can get to see any log about extensions, then i might be able to guess what is going wrong, but I couldn't find anything.
2. Are there any known compatibility problems with Windows Vista?
3. What can I do to diagnose this problem?

One interesting note; In Windows XP, if I change the file name of the extension to some name that does not start with 'Vegas' then Vegas does not load it.
jetdv wrote on 9/25/2009, 6:24 AM
You should be able to name them anything at all. They definitely do not have to start with the word "Vegas". "Excalibur.dll", "ProjectInspector.dll", and "AutoSave.dll" all load just fine for me on both XP and Vista and both 32-bit and 64-bit.

Are you compiling for and running in the same version of Vegas? For example, if I compile on the 8.0c Vegas dlls, I won't be able to run it in 8.0a. Compiling on the 8.0a dlls will run in 8.0c (and 9.0x).

It sounds like your installation folder is fine. {My Documents}\Vegas Application Extensions is a checked folder.

Does it not even show up in the menu at all? Or does it not start? Either way, I would add logging to YOUR dll. If Vegas attempts to start it, your dll could then output to a log what it's doing on startup.
JohnnyRoy wrote on 9/25/2009, 6:44 AM
> It does not show any error. I don't know where to look for logs.

Since this is your code, I recommend that you bring it up in a debugger and see where it's failing. As Edward said, you need to log in your code if you expect to see logs.

If you've never written an extension before, you might try compiling the web browser sample in the SDK and make sure that works so that you know that your development environment is set up correctly first.

~jr
ibrahimdursun wrote on 9/30/2009, 10:57 PM
Thanks Edward and Johnny!

>Are you compiling for and running in the same version of Vegas? For example, if I >compile on the 8.0c Vegas dlls, I won't be able to run it in 8.0a. Compiling on the >8.0a dlls will run in 8.0c (and 9.0x).

Yes it was not the Vista but the referenced dll's. My extension was compiled with Vegas 9.0a dlls and tested against Vegas 9.0b hence my extension was not being loaded. This didn't occur to me before.

Thanks in advance.