Microsoft.Vsa.VsaException: AssemblyExpected

RichMacDonald wrote on 2/19/2005, 10:17 AM

Just trying to get going using C# to develop scripts. java programmer thus newbie to C#. I've installed .NET Framework SDK 2.0 and the DirectX 9.0 SDK. . I downloaded the peachrock VegasHello project and built the project. Running the script in Vegas5 I get the error: "Microsoft.Vsa.VsaException: AssemblyExpected (0x80133004): C:\Program Files\Sony\Vegas 5.0\Script Menu\Hello\VegasHello.dll". I've tried to do this with the Microsoft Visual C# Express Edition Beta and with nant with the same results. In the js.config file I've used both the "isLocal" option and the full pathname. No difference. I don't know where all the good help forums are for C# and my google search on the error came up with nothing. Obviously this is a simple configuration error, but I'm not sure what to do next. Any help appreciated. TA.

Comments

rcampbel wrote on 2/19/2005, 3:51 PM

Rich,

Vegas is using the .Net Framework 1.1 for scripts. I think that you are getting this error since you built the dll with the 2.0 SDK and Express. The Express beta will not build a .Net 1.1 dll to my knowledge (I tried it once when it first came out but it messed up things on my machine so I removed it).

You will need to build the dll using the .Net Framework 1.1 using either Sharp Develop or Visual Studio C# Standard 2003. You can also build with the command line tools, but it is a bit harder. I recommend VS C# Standard 2003. You can get it for around $100.

Randall

RichMacDonald wrote on 2/19/2005, 8:46 PM

>I think that you are getting this error since you built the dll with the 2.0 SDK and Express.

Ah, I figured I had one too many betas. I removed the net framework 2.0 but that didn't fix the problem, so it fingered either the express beta or Microsoft's usual inability to remove an app once installed. Annoying that it's probably the express beta. I'll keep checking some things out. Thanks for the experience report.

EDIT: Actually when I removed the .framework 2.0 it did fix the problem. And the C# express beta loads but refuses to open or create a project without the .net framework 2.0. My "initial unload" of 2.0 appears to have been flaky. What didn't work 5 hrs ago does work now and vice-versa.

rcampbel wrote on 2/19/2005, 10:30 PM

It seems that MS wants to tie each version of a .Net VS to a single framework. Don't know why they can't have a VS that will develop to any target version of the framework.

I don't think that the 2.0 SDK is quite ready for prime time. I had to manually remove some things (don't remember what) to get 1.1 fully operational again.

Randall