Nope, no GUI as of yet. I haven't been at this whole thing for very long.

I did come across something, though:

I've recently started using the Hashtable class to speed up e.g. matching Event names against Region names, and it seems the .NET 1.1 implementation doesn't support the Item() method. I can't really say how, but somehow VS "knew" I was targetting 1.1, and wouldn't let me use the Item() method. So it would seem that you can, in some sense, limit VS to .NET 1.1 specifications.

Again, I'm a complete noob, so I can't really offer a good explanation or help you very much.

A brief update: No, the GUI Designer doesn't work in the projects I've set up. I've tried several workarounds, and the most stable seems to be opening a separate solution for desiging GUI:s and then moving that project into your Vegas solution ("rendering" it, in a sense).

This is obviously a tiresome workaround, so I've stuck to writing most of my GUI code manually. It's bit of a bitch, but then again I haven't really made any humongous GUI projects yet.

This is why I still use Visual Studio 2003 for Vegas scripts. No workarounds. It simply works like it's supposed to.

~jr

That makes sense, yes. Well, it'll be a moot problem soon enough, as Vegas 7 supports .NET 2.0.

> Well, it'll be a moot problem soon enough, as Vegas 7 supports .NET 2.0.

As long as you are writing scripts for yourself or you are only sharing your scripts with Vegas 7 users. Otherwise if you need backward compatibility you need to continue to use Visual Studio 2003 and .NET 1.1 to stay compatible with Vegas 5 & 6. I don't know how many people have upgraded to Vegas 7 but people are still using Vegas 4 (which is another script nightmare on its own)

~jr

No, I'm an in-house sound designer - my scripts currently satisfy the very modest demographic of two people =)

I've moved on to .NET 2.0 now, by the way. The VS Designer is very convenient, but I've noticed that the event handler functions retain their generic names (button1, checkbox2 etc) even though I rename the controls to more semantic names (btnOK, cbRenderRegions). Any way around that, or am I stuck with manually editing the "forbidden" auto-code?

> even though I rename the controls to more semantic names (btnOK, cbRenderRegions). Any way around that, or am I stuck with manually editing the "forbidden" auto-code?

You have to rename the control BEFORE you create the event handler. Once you double-click on a control and create a handler, the handler will take on the name of the control at that time. So if the control is named button1 when you create the handler, the handler will be button1_Clicked. But if you rename the button to bntOK and THEN create the handlers the handler will be called bntOK_Clicked. I always rename my controls as soon as I drop them on the form so I don't forget and create generic named handlers.

~jr