AGVS

[Clarvalon]

It's a nice idea but I'm yet to be convinced by the benefits.  Creating GUIs in Visual Studio is generally fine, though it does have its quirks.  With C# scripting I can see an obvious benefit but with GUI creation I may be missing something.

The bigger issue is that to make it work you'd need a dependancy at design time on System.Windows.Forms.  At runtime this dependancy cannot be in place, as it will be unsupported on most target platforms (Xbox, Silverlight etc).  Swapping this dependancy at compile time is an option, though things start to get messy quickly.  I'm not aware of any other way around it.

[Clarvalon]

Apologies for resurrecting an old thread, but I've a follow up to the previous posts on my blog that may be of some interest:  http://clarvalon.blogspot.com/2011/09/new-direction.html

The gist of it is this - I've had a rethink with regards to the AGS to XAGE conversion process.  XAGE no longer uses it's proprietary scripting system and is instead being updated to use C# as a scripting language.  As part of the working prototype I've captured various standard AGS functions via a C# Interface and I'm now in the process of implementing them within the XAGE Engine.

I feel like I've addressed all the initial pitfalls of the technique detailed above, though if anyone is aware of any potential (or glaring) obstacles I've overlooked then I'd be glad to hear them before I plough the next few months of my life into this.

[Wonkyth]

Every time I hear mention of this, it sounds even better!